Add the beginnings of a GENERIC_V5 kernel that targets armv5 boards and
uses FDT.

In this first iteration some support is added for OLinuXino boards.

Thanks to Yuri Honegger for doing the vast majority of the work.

Utilite has console on uart4.

arm: dts: adapt for dts-5.15

branches: 1.1.2;
add dts for odroid-N2 plus

arm: dts: adapt for dts-5.15

#include_next confuses clang-cpp; use relative pathname to upstream dts

warning: #include_next in file found relative to primary source file or
found by absolute path; will search from start of include path
[-Winclude-next-absolute-path]
error: #include nested too deeply

Catch up to recent mainline dts changes

branches: 1.3.2; 1.3.6; 1.3.8;
Add Amlogic Meson SDHC driver (non-standard bindings)

Add (non-standard) fb node for meson8b

Add support for (FDT-ized) Amlogic Meson8b.

arm: dts: adapt for dts-5.15

Catch up to recent mainline dts changes

Updates to get Odroid-C1 in better shape since the last DTS import

branches: 1.5.2; 1.5.6; 1.5.8;
Add rtc node (non-standard bindings)

Add operating points and clocks for CPUs

Add Amlogic Meson SDHC driver (non-standard bindings)

Add (non-standard) fb node for meson8b

Add support for (FDT-ized) Amlogic Meson8b.

delete attribution per request of contributor

branches: 1.2.4;
#include_next confuses clang-cpp; use relative pathname to upstream dts

warning: #include_next in file found relative to primary source file or
found by absolute path; will search from start of include path
[-Winclude-next-absolute-path]
error: #include nested too deeply

branches: 1.1.2;
Set the stdout-path on xM like Ti OMAP3 BeagleBoard

branches: 1.2.4;
#include_next confuses clang-cpp; use relative pathname to upstream dts

warning: #include_next in file found relative to primary source file or
found by absolute path; will search from start of include path
[-Winclude-next-absolute-path]
error: #include nested too deeply

branches: 1.1.2;
Set stdout-path on TI OMAP3 BeagleBoard

branches: 1.2.4;
#include_next confuses clang-cpp; use relative pathname to upstream dts

warning: #include_next in file found relative to primary source file or
found by absolute path; will search from start of include path
[-Winclude-next-absolute-path]
error: #include nested too deeply

branches: 1.1.2;
Use dss as console on Nokia N900.

branches: 1.1.2;
enable rkv1crypto on rock64.

this comes from upstream d1152bc533c941f7e267bf53d344cee510ea2808.

(i tried to make this be in rk3328.dtsi so all rk3328 boards would
benefit, but it doesn't work, and this is the only one have to test.)

adjust rkv1crypto to support a per-platform clocks setup.

branches: 1.1.2;
Enable rkv1crypto on nanopi-r2s

Follow the example of rock64. Tested by myself.

branches: 1.8.2;
enable rkv1crypto on rock64.

this comes from upstream d1152bc533c941f7e267bf53d344cee510ea2808.

(i tried to make this be in rk3328.dtsi so all rk3328 boards would
benefit, but it doesn't work, and this is the only one have to test.)

adjust rkv1crypto to support a per-platform clocks setup.

arm: dts: adapt for dts-5.15

begin to make rock64 audio work.

- set status for "analog_sound" to enabled.
- add clocks for the i2s and spdif nodes.
- match "rockchip,rk3066-i2s", "rockchip,rk3188-i2s",
and "rockchip,rk3288-i2s".

this gets i2s and ausoc to attach, but no audio(4) yet.

to complete this probably also needs a codec driver (appears
to be rk3328 specific, unlike eg pinebookpro's es8316), and
support for "audio-graph-card" type sound cards.

branches: 1.5.8;
Enable USB3 support on RK3328

branches: 1.4.2;
Remove vcc_host1_5v hack now that fixedregulator honours pin polarity

Swap polarity of the vcc_host1_5v pin to enable USB power

it's called "snps,dis_u2_susphy_quirk" in both upstream and what
our drivers expect, not "snps,dis-u2-susphy-quirk".

unfortunately, my rock64 usb still seems to be non functional.

from jmcneill@.

branches: 1.1.2; 1.1.4;
Enable DWC3 USB DRD (host mode) on Rock64.

arm: dts: adapt for dts-5.15

Enable USB3 support on RK3328

branches: 1.1.2; 1.1.4; 1.1.8;
Enable DWC3 USB DRD (host mode) on Rock64.

branches: 1.1.2;
Rockchip crypto engine RNG driver.

As found on the rk3288 and rk3399. This driver only supports the
TRNG, not the rest of the crypto engine, although it uses the AES unit
to do a self-test at attach time to verify that the engine works.

There seem to be two versions of the Rockchip crypto engine, v1 and
v2; this one is for v1. Can't name a driver `rkcryptov1' so we'll
clumsily call it `rkv1crypto' instead to leave room for `rkv2crypto'
later on.

The crypto binding derived from the Rockchip BSP Linux kernel, in the
location it appears on the rk3399, is in rk3399-crypto.dtsi, since
there doesn't seem to be a better place to put it at the moment among
this twisty maze of inclusions, all different.

branches: 1.1.4;
Enable rkv1crypto on nanopi-r4s

apply a DTS change from upstream to reduce pwm frequency for the backlight.

should fix buzzing sometimes seen with the display. do this as an override
rather than patching the dts source. (tested with a hack to ensure that
the new value is set in the configuration.)

XXX: pullup-10, perhaps pullup-9.

upstream commit message:


arm64: dts: rockchip: Raise Pinebook Pro's panel backlight PWM frequency

Increase the frequency of the PWM signal that drives the LED backlight of
the Pinebook Pro's panel, from about 1.35 KHz (which equals to the PWM
period of 740,740 ns), to exactly 8 kHz (which equals to the PWM period of
125,000 ns). Using a higher PWM frequency for the panel backlight, which
reduces the flicker, can only be beneficial to the end users' eyes.

On top of that, increasing the backlight PWM signal frequency reportedly
eliminates the buzzing emitted from the Pinebook Pro's built-in speakers
when certain backlight levels are set, which cause some weird interference
with some of the components of the Pinebook Pro's audio chain.

The old value for the backlight PWM period, i.e. 740,740 ns, is pretty much
an arbitrary value that was selected during the very early bring-up of the
Pinebook Pro, only because that value seemed to minimize horizontal line
distortion on the display, which resulted from the old X.org drivers causing
screen tearing when dragging windows around. That's no longer an issue, so
there are no reasons to stick with the old PWM period value.

The lower and the upper backlight PWM frequency limits for the Pinebook Pro's
panel, according to its datasheet, are 200 Hz and 10 kHz, respectively. [1]
These changes still leave some headroom, which may have some positive effects
on the lifetime expectancy of the panel's backlight LEDs.

[1] https://files.pine64.org/doc/datasheet/PinebookPro/NV140FHM-N49_Rev.P0_20160804_201710235838.pdf

Fixes: 5a65505a6988 ("arm64: dts: rockchip: Add initial support for Pinebook Pro")
Cc: stable@vger.kernel.org
Reported-by: Nikola Radojevic <nikola@radojevic.rs>
Signed-off-by: Dragan Simic <dsimic@manjaro.org>
Tested-by: Nikola Radojevi# <nikola@radojevic.rs>
Link: https://lore.kernel.org/r/2a23b6cfd8c0513e5b233b4006ee3d3ed09b824f.1722805655.git.dsimic@manjaro.org
Signed-off-by: Heiko Stuebner <heiko@sntech.de>

branches: 1.7.6;
Enable crypto engine on Pinebook Pro.

Only used for rng at present.

don't disable the spi any more. it works fine (and i'm booting
from it on one pbp directly to nvme.)

arm: dts: adapt for dts-5.15

default RK3399 PCIe to 1.x.

sometime in mid-2019, rockchip disabled PCIe 2.x referrencing a
non-public errata in linux and the dts, both of which were changed
to default to only PCIe 1.x (in code, and in DT.) see:

https://lore.kernel.org/all/1481881357-1793-1-git-send-email-shawn.lin@rock-chips.com/

we haven't observed any specific problems, but we've also tested
far fewer cards than linux. there are other issues such as what
happens for a PCI abort depending on which CPU triggers it we do
not currently handle either.

tested on rockpro64 with nvme & ahcisata, and pinebook pro nvme.

still allows DT to set back to '2' if the user so desires.

Rockchip crypto engine RNG driver.

As found on the rk3288 and rk3399. This driver only supports the
TRNG, not the rest of the crypto engine, although it uses the AES unit
to do a self-test at attach time to verify that the engine works.

There seem to be two versions of the Rockchip crypto engine, v1 and
v2; this one is for v1. Can't name a driver `rkcryptov1' so we'll
clumsily call it `rkv1crypto' instead to leave room for `rkv2crypto'
later on.

The crypto binding derived from the Rockchip BSP Linux kernel, in the
location it appears on the rk3399, is in rk3399-crypto.dtsi, since
there doesn't seem to be a better place to put it at the moment among
this twisty maze of inclusions, all different.

branches: 1.2.4; 1.2.8;
Disable SPI for now (rkspi driver hangs at boot)

Add Pinebook Pro dts, from Manjaro Linux.

https://gitlab.manjaro.org/tsys/linux-pinebook-pro/blob/877ca0e7283596f37845de50dc36bff5b88b91e1/arch/arm64/boot/dts/rockchip/rk3399-pinebook-pro.dts

Re-enable the fan.

arm: dts: adapt for dts-5.15

default RK3399 PCIe to 1.x.

sometime in mid-2019, rockchip disabled PCIe 2.x referrencing a
non-public errata in linux and the dts, both of which were changed
to default to only PCIe 1.x (in code, and in DT.) see:

https://lore.kernel.org/all/1481881357-1793-1-git-send-email-shawn.lin@rock-chips.com/

we haven't observed any specific problems, but we've also tested
far fewer cards than linux. there are other issues such as what
happens for a PCI abort depending on which CPU triggers it we do
not currently handle either.

tested on rockpro64 with nvme & ahcisata, and pinebook pro nvme.

still allows DT to set back to '2' if the user so desires.

rk3399 pcie: pay attention to the "bus-scan-delay-ms" property.

our existing pinebookpro DTS, but not the other rk3399 ones, have
this property set to "1000" (it's the same in linux 5.14 DTS.)

as there are already static 100ms + upto 1000ms, count how many
are done, and only delay more to complete one second.

this allows reverting this device-specific change:

http://mail-index.netbsd.org/source-changes/2021/06/23/msg130402.html

and makes other sorts of storage cards more likely to work as well.

tested on rockpro64.

XXX: consider moving dts setting into rk3399.dtsi.

ok jmcneill jak


inspired by https://gitlab.manjaro.org/manjaro-arm/packages/core/linux/-/blob/master/0013-rk3399-rp64-pcie-Reimplement-rockchip-PCIe-bus-scan-delay.patch

Rockchip crypto engine RNG driver.

As found on the rk3288 and rk3399. This driver only supports the
TRNG, not the rest of the crypto engine, although it uses the AES unit
to do a self-test at attach time to verify that the engine works.

There seem to be two versions of the Rockchip crypto engine, v1 and
v2; this one is for v1. Can't name a driver `rkcryptov1' so we'll
clumsily call it `rkv1crypto' instead to leave room for `rkv2crypto'
later on.

The crypto binding derived from the Rockchip BSP Linux kernel, in the
location it appears on the rk3399, is in rk3399-crypto.dtsi, since
there doesn't seem to be a better place to put it at the moment among
this twisty maze of inclusions, all different.

add template bits for optional eDP panel on RockPro64

Enable HDMI audio on ROCKPro64

rk3399-rockpro64.dts: enable spi1 and add spiflash as a child node

branches: 1.7.2;
Set max link speed, remove assigned clocks

Enable RK3399 PCIe.

branches: 1.5.2;
Enable pwm1 and add a pwm-fan node to enable the +FAN- header on ROCKPro64

Use mainline dts for rockpro64 now.

Revert RockPro64 dts changes made for rk3399_pcie. This will need to
be re-done differently so as to avoid contention between dts upstream
and our driver.

Add RK3399 PCIe host bridge support.

Not enabled yet due to occasional hangs during boot, and needing
__BUS_SPACE_HAS_PROBING_METHODS enabled.

Uses slightly non-standard DT bindings to avoid suboptimality of the
Linux binding. This allows for much more flexibility and efficency
in allotment of the limited apertures into PCI spaces.

branches: 1.1.2;
Add dts for ROCKPro64

Disable private timer whose new driver clashes with the global timer's one.

Stopgap measure to make the DE0 Nano Soc work again, targeted for netbsd-9
pullup. We'll see later if we switch to using the private timer.

branches: 1.2.4; 1.2.6;
Update for 4.20.3 dts changes

branches: 1.1.2;
Rename the DE0 Nano SoC dts file to its new linux/uboot name

Rename the DE0 Nano SoC dts file to its new linux/uboot name

Add reset information for first watchdog timer

branches: 1.1.2;
Add support for the DE0 NanoSoC board.

It's Cyclone V based and thus includes a dual-core Cortex A9 @925MHz.
Most standard peripherals are supported (USB, SDCard, Ethernet) and
no unusual peripheral is supported yet (FPGA, GPIO, ...)

arm: dts: adapt for dts-5.15

Enable HDMI audio support on Pine64, Pine64+, and Pine64 LTS boards.

branches: 1.2.2; 1.2.6; 1.2.10;
Enable USB-OTG-EHCI and USB-OTG-OHCI controllers on Pine64+.

Enable ethernet on Pine64+

Enable HDMI audio support on Pine64, Pine64+, and Pine64 LTS boards.

branches: 1.1.4; 1.1.8;
Add wrapper for Pine64 (non-plus) dts

arm: dts: adapt for dts-5.15

lcd_rgb666_pins is in sun50i-a64.dtsi now so we don't need it here.

Enable HDMI and HDMI audio

branches: 1.16.2;
Remove audio related nodes (they are present in mainline dts now)

Add eDP transmitter and enable display pipeline

Update for 4.20.3 dts changes

pull across this patch:

https://github.com/anarsoul/linux-2.6/commit/26b3d6f8ffa77cb05066c11967a498d6dacbdc42#diff-61a0580c3eaa34a373cc7ee7ee46dd2a

---
arm64: allwinner: a64: enable Bluetooth On Pinebook

Pinebook has an RTL8723CS WiFi + BT chip, BT is connected to UART1
and uses PL4 as BT reset, PL5 as device wake GPIO, PL6 as host wake GPIO
the I2C controlling signals are connected to R_I2C bus.

Enable it in the device tree.

Signed-off-by: Vasily Khoruzhick <anarsoul@gmail.com>
---

this enables:

[ 1.000019] com1 at simplebus1: ns16550a, working fifo
[ 1.000019] com1: interrupting on GIC irq 33

to attach. more work with firmware and btattach will be required,
for the BT to be actually functional.

Make brightness-levels available in increments of 10% from 0 to 100, and set the default brightness level to match the one used by U-Boot (30%)

branches: 1.11.2;
Add cpu0 supply and operating points table

Disable spdif nodes on pinebook

Enable audio codec

Add backlight node and enable pwm

Enable ehci0/ohci0 (attached to left USB port)

Enable mmc1 (SDIO Wi-Fi is attached here)

Pinebook is not based on Pine64, so do not derive from its dts

Add support for Pinebook lid switch and eMMC

branches: 1.3.2;
Pinebook LCD pipeline is mixer0-lcd0

branches: 1.2.2;
Correct model and compatible string for Pinebook

Add Pinebook support.

arm: dts: adapt for dts-5.15

Enable DVFS

Revert previous. Apparently it's wrong.

PR/56095 SOPINE Clusterboard unable to transmit network data

Add allwinner,tx-delay-ps = <500> using the diff supplied by tnn@

branches: 1.2.12;
Enable HDMI audio support on Pine64, Pine64+, and Pine64 LTS boards.

branches: 1.1.2; 1.1.4; 1.1.8;
Add extra sun50i-a64 nodes to SoPine Baseboard dts.

arm: dts: adapt for dts-5.15

Add crypto engine block.

Enable HDMI audio support on Pine64, Pine64+, and Pine64 LTS boards.

Fix PMU interrupt numbers on Allwinner A64.

branches: 1.11.2;
Remove audio related nodes (they are present in mainline dts now)

Update for 4.20.3 dts changes

branches: 1.9.2;
Add cpu0 clock

Add audio codec nodes

Add pwm node

Add A64 thermal sensor node

Upstream dts specifies emac for sun50i-a64 now

branches: 1.4.2; 1.4.4;
Switch to new emac bindings for H3 boards

Enable USB-OTG-EHCI and USB-OTG-OHCI controllers on Pine64+.

Add simplefb stub for Allwinner A64

Enable ethernet on Pine64+

arm: dts: adapt for dts-5.15

branches: 1.1.4;
- correct cpu voltage
- add cpu speed table
- include sun50i-h5.dtsi
Now thermal sensors and cpu speed control work

arm: dts: adapt for dts-5.15

Increase voltage for frequencies above 1GHz

branches: 1.3.4;
catch up to upstream dts changes/additions

branches: 1.2.2; 1.2.4;
Enable CPU frequency scaling and thermal sensors.

Enable Gigabit Ethernet on Nano Pi Neo Plus 2.

arm: dts: adapt for dts-5.15

arm/sunxi: Wire up sun8icrypto(4) on Allwinner H5.

Tested on NanoPi Neo PLUS2.

branches: 1.1.8;
Add support for H5 simple framebuffer, CPUX clocks, R_I2C controller, SID
controller, and thermal sensors.

arm: dts: adapt for dts-5.15

branches: 1.1.2;
Add a more complete / correct device tree for the OrangePi Lite 2.

Add "nextthing,pocketchip" to the head of the 'compatible' property
so that this device tree can be distinguished from that of the base
CHIP. "nextthing,chip" remains in the list, but one match-priority
notch down.

branches: 1.1.2; 1.1.6;
Add a PocketCHIP -specific dts with information about the keyboard and
touch screen.

arm: dts: adapt for dts-5.15

branches: 1.1.8;
Add spiflash support in GENERIC
Add a dts enabling spi0 and attaching the SPI flash for newer lime2-emmc
boards.

No need to define our own emac node as this is in the upstream dts now.

branches: 1.1.2; 1.1.4; 1.1.6;
add emac to bananapi m3 dts

remove clause 3 from all my licenses that aren't conflicting with
another copyright claim line. again. (i did this in 2008 and then
did not update all of my personal templates.)

branches: 1.1.2;
the standard sun8i-a83t-cubietruck-plus.dts is missing temp sensor
support that is in sun8i-a83t.dtsi. this one includes both.

arm: dts: adapt for dts-5.15

Add thermal sensor node

No need to define our own emac node as this is in the upstream dts now.

branches: 1.1.2; 1.1.4; 1.1.6;
add emac to bananapi m3 dts

branches: 1.1.2;
Add a device tree for the Banana Pi BPI-P2 Zero. This device is
based on the BPI-M2 Zero, with a couple of small changes:
- On-board Ethernet (with optional PoE support)
- On-board eMMC.
- Card-detect for the SD card slot is wired up a little differently.

Kindly tested by Dima Veselov.

arm: dts: adapt for dts-5.15

branches: 1.1.2; 1.1.10;
Add sun8i-h3-nanopi-r1.dts and sun8i-h3-nanopi-duo2.dts.

From https://github.com/armbian/build/blob/master/patch/kernel/sunxi-next/xxx-add-nanopi-r1-and-duo2.patch

arm: dts: adapt for dts-5.15

Enable audio codec

branches: 1.2.8;
Enable emac for NanoPi M1

Wrap NanoPi M1 dts to enable simplefb support.

arm: dts: adapt for dts-5.15

Mainline dts has switched to operating-points-v2

branches: 1.3.2; 1.3.6;
Switch to new emac bindings for H3 boards

add cpu regulator and operating points for nanopi neo

branches: 1.1.4; 1.1.6;
Add local patches to sun8i-h3-orangepi-plus2e and sun8i-h3-nanopi-neo to
enable ethernet support.

arm: dts: adapt for dts-5.15

branches: 1.3.8;
To quote the upstream change "Remove useless pinctrl nodes"

branches: 1.2.2;
Cherry pick a few changes from the armbian u-boot patch.

Makes my NanoPi R1 boot reliably.
From https://github.com/armbian/build/blob/master/patch/u-boot/u-boot-sunxi/add-nano+pi-r1-and-duo2.patch

Add sun8i-h3-nanopi-r1.dts and sun8i-h3-nanopi-duo2.dts.

From https://github.com/armbian/build/blob/master/patch/kernel/sunxi-next/xxx-add-nanopi-r1-and-duo2.patch

Remove now-unneeded and brocken (probably since dts-5.15 import)
sun8i-h3-orangepi-one.dts, and let the build use the one from sys/external.
Problem reported and fix tested by Dave Tyson as reported on port-arm@
While there remove #include "sun8i-h3.dtsi" from sun8i-h3-orangepi-plus2e.dts,
this file has been removed with the dts-5.15 import.

branches: 1.3.2; 1.3.36;
Re-add this, it is still needed for simplefb

Switch to new emac bindings for H3 boards

Add local patches to sun8i-h3-orangepi-one to enable HDMI support.

Remove now-unneeded and brocken (probably since dts-5.15 import)
sun8i-h3-orangepi-one.dts, and let the build use the one from sys/external.
Problem reported and fix tested by Dave Tyson as reported on port-arm@
While there remove #include "sun8i-h3.dtsi" from sun8i-h3-orangepi-plus2e.dts,
this file has been removed with the dts-5.15 import.

branches: 1.4.28;
Mainline dts has switched to operating-points-v2

branches: 1.3.2; 1.3.6;
Switch to new emac bindings for H3 boards

Add operating points for OrangePi Plus2E and enable cpufreq scaling.

branches: 1.1.4; 1.1.6;
Add local patches to sun8i-h3-orangepi-plus2e and sun8i-h3-nanopi-neo to
enable ethernet support.

arm: dts: adapt for dts-5.15

branches: 1.6.2;
Switch to new emac bindings for H3 boards

add thermal sensor controller

add Security ID EFUSE node

Add operating points for OrangePi Plus2E and enable cpufreq scaling.

Add a simplefb node for H3 SoCs

branches: 1.1.4; 1.1.6;
Add local patches to sun8i-h3-orangepi-plus2e and sun8i-h3-nanopi-neo to
enable ethernet support.

branches: 1.1.2;
Enable USB2 controllers on Cubieboard4.

Add a device tree for the Red Pitaya SDRlab 122-16.

To boot NetBSD on the 122-16, copy the .dtb built from
zynq-red-pitays-122-16.dts, the first-stage bootloader (called
boot.bin) and U-Boot that came with the 122-16 and a kernel image,
netbsd.ub, built for earmv7hf to an MS-DOS partition on an
MBR-partitioned SD card. At the U-Boot prompt, "Zynq> ", type these
commands:

i2c dev 0
eeprom read 0 0x50 0 0x1804 0x400
env import -b 0 0x400 hw_rev serial ethaddr
setenv bootargs "root=ld0a"
fatload mmc 0 0x01f00000 device~1.dtb
fatload mmc 0 0x02000000 netbsd.ub
fdt addr 0x01f00000
fdt set /axi/ethernet@e000b000 local-mac-address $ethaddr
bootm 0x02000000 - 0x01f00000

Note that the ethernet PHY will not attach unless you have applied
the patches from Lloyd Parkes in kern/58083.

Device tree overlay for the FriendlyARM NanoPi NAS Dock for the NanoPi NEO,
NEO Air, and NEO2.

branches: 1.1.8;
Add a device tree Overlay for the Orange Pi Zero NAS expansion board for
Orange Pi Zero and Orange Pi Zero Plus.