I accidently didnt save the Patch Version on the first email, it's the
same patch but with fixed versioning. It was an accident, sorry.
Am Di., 15. Okt. 2024 um 21:29 Uhr schrieb Cenk Uluisik
<cenk.uluisik@xxxxxxxxxxxxxx>:
Implements a slightly modified rk3588s-orangepi-5b.dts from thehttps://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git/
vendor.
Unfortunately the &wireless_bluetooth and &wireless_wlan are not
implemented yet.
Bigger parts of the rk3588s-orangepi-5.dts file were moved into a
new
rk3588s-orangepi-5.dtsi file, so that both device trees from the
orangepi-5 and 5b include from it and avoid including from the .dts.
This changes the Orange Pi 5's sdmmc alias to be mmc1, breaking
existing
users if they used the /dev/mmc0 device file, so it's consistent
with all
the other rk3588 DTS, which, is also the new default that rockchip
wants
to use.
https://github.com/orangepi-xunlong/linux-orangepi/commit/
bce92d16b230b8e93c2831fb7768839fd7bbab04
Therefore add the sdhc alias to be mmc0 on the
rk3588s-orangepi-5b.dts.
The "enable-active-low" warning is addressed here:
commit/?h=v6.12-armsoc/dtsfixes&id=f4d29bebaa6118c1e51e8f1c21ce2b34f43e1479
The "leds-gpio" warning was already there because the DTS checking
script
might not like the ID, which is probably avoidable by renaming it,
but this
will be addressed in a seperate issue.
How does this board differ from the original Orange Pi 5?
- the Orange Pi 5 has a M.2 NVMe M-key PCI 2.0x1
slot (hooked to combphy0_ps) whereas the Orange Pi 5b uses
combphy0_ps
for the WiFi.
- The Orange Pi 5 with the M.2 socket has a regulator defined
hooked to
"GPIO0_C5" (i.e. PCIE_PWREN_H) whereas the Orange Pi 5B has
GPIO0_C5
hooked to BT_WAKE_HOST.
- builtin eMMC storage
- no SPI NOR flash (u-boot, preboot etc. initiates
from within the eMMC
storage)
- ap6275p Wifi module (like the Orange Pi 5 Plus)
- builtin BlueTooth module
Signed-off-by: Cenk Uluisik <cenk.uluisik@xxxxxxxxxxxxxx>