Linux 5.12 on N10

After updating the N10 to mainline u-boot, I have now updated kernel to 5.12 and is running on the N10, with the Ubuntu 18.04 which has been upgraded to 20.04.2.

dtb errors on mainline - to be checked.

dw-apb-uart ff180000.serial: failed to request DMA
dwmmc_rockchip fe310000.mmc: Looking up vmmc-supply property in node /mmc@fe310000 failed
dwmmc_rockchip fe310000.mmc: Looking up vmmc-supply property in node /mmc@fe310000 failed
dwmmc_rockchip fe310000.mmc: Looking up vmmc-supply property in node /mmc@fe310000 failed
dwmmc_rockchip fe310000.mmc: Looking up vqmmc-supply property in node /mmc@fe310000 failed
dwmmc_rockchip fe310000.mmc: Looking up vqmmc-supply property in node /mmc@fe310000 failed
dwmmc_rockchip fe310000.mmc: Looking up vqmmc-supply property in node /mmc@fe310000 failed
dwmmc_rockchip fe320000.mmc: Looking up vmmc-supply property in node /mmc@fe320000 failed
of_get_named_gpiod_flags: can't parse 'dvs-gpio' property of node '/i2c@ff3c0000/pmic@20[0]'
of_get_named_gpiod_flags: can't parse 'dvs-gpio' property of node '/i2c@ff3c0000/pmic@20[1]'
of_get_named_gpiod_flags: can't parse 'dvs-gpios' property of node '/i2c@ff3c0000/pmic@20[0]'
of_get_named_gpiod_flags: can't parse 'dvs-gpios' property of node '/i2c@ff3c0000/pmic@20[1]'
of_get_named_gpiod_flags: can't parse 'gpio' property of node '/vcc12v-dcin-regulator[0]'
of_get_named_gpiod_flags: can't parse 'gpio' property of node '/vcc5v0-sys-regulator[0]'
of_get_named_gpiod_flags: can't parse 'gpios' property of node '/vbus-host[0]'
of_get_named_gpiod_flags: can't parse 'gpios' property of node '/vbus-typec[0]'
of_get_named_gpiod_flags: can't parse 'gpios' property of node '/vcc12v-dcin-regulator[0]'
of_get_named_gpiod_flags: can't parse 'gpios' property of node '/vcc5v0-sys-regulator[0]'
of_get_named_gpiod_flags: can't parse 'gpios' property of node '/vcc-pcie-regulator[0]'
of_get_named_gpiod_flags: can't parse 'rs485-term-gpio' property of node '/serial@ff180000[0]'
of_get_named_gpiod_flags: can't parse 'rs485-term-gpio' property of node '/serial@ff1a0000[0]'
of_get_named_gpiod_flags: can't parse 'rs485-term-gpios' property of node '/serial@ff180000[0]'
of_get_named_gpiod_flags: can't parse 'rs485-term-gpios' property of node '/serial@ff1a0000[0]'
of_get_named_gpiod_flags: can't parse 'snps,reset-gpios' property of node '/ethernet@fe300000[0]'
of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/efuse@ff690000[0]'
of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/mmc@fe310000[0]'
of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/mmc@fe310000[0]'
of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/mmc@fe310000[0]'
of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/mmc@fe320000[0]'
of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/mmc@fe330000[0]'
of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/efuse@ff690000[0]'
of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/mmc@fe310000[0]'
of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/mmc@fe310000[0]'
of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/mmc@fe310000[0]'
of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/mmc@fe320000[0]'
of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/mmc@fe330000[0]'
phy phy-ff770000.syscon:pcie-phy.4: Looking up phy-supply property in node /syscon@ff770000/pcie-phy failed
phy phy-ff770000.syscon:pcie-phy.5: Looking up phy-supply property in node /syscon@ff770000/pcie-phy failed
phy phy-ff770000.syscon:pcie-phy.6: Looking up phy-supply property in node /syscon@ff770000/pcie-phy failed
phy phy-ff770000.syscon:pcie-phy.7: Looking up phy-supply property in node /syscon@ff770000/pcie-phy failed
phy phy-ff770000.syscon:phy@f780.0: Looking up phy-supply property in node /syscon@ff770000/phy@f780 failed
phy phy-ff7c0000.phy.8: Looking up phy-supply property in node /phy@ff7c0000/dp-port failed
phy phy-ff7c0000.phy.9: Looking up phy-supply property in node /phy@ff7c0000/usb3-port failed
rockchip-iodomain ff770000.syscon:io-domains: Looking up audio-supply property in node /syscon@ff770000/io-domains failed
sdhci-arasan fe330000.mmc: Looking up vmmc-supply property in node /mmc@fe330000 failed
sdhci-arasan fe330000.mmc: Looking up vqmmc-supply property in node /mmc@fe330000 failed
vcc5v0_usb2: failed to get the current voltage: -EPROBE_DEFER
vcc5v0_usb2: will resolve supply early: vcc9
vcc5v0_usb2: supplied by vcc5v0_sys
vcc5v0_usb2: 5000 mV, disabled
vccio_3v3: failed to get the current voltage: -EPROBE_DEFER
vccio_3v3: will resolve supply early: vcc8
vccio_3v3: supplied by vcc3v3_sys
vccio_3v3: 3300 mV, enabled

The full dmesg is at:

Kernel .config:

FYI. Update on the upstreaming of the regulator (gpu)

https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git/commit/?id=5eee5eced95f1b35c8567688ed52932b7e58deee

1 Like

Hi heitbaum!

In regards to building Lniux 5.12, do you just checkout 5.12 from upstream and use the .config you’ve provided?

Pretty much.
Go with 5.13-rc6
I’ll update my LE10 branch this weekend with all my bits/pieces.
https://github.com/heitbaum/LibreELEC.tv/commits/dev-rk.
They are all in (dev) now but it is a bit of a mess to extract.

Armbian test builds (untested) https://imola.armbian.com/dl/rockpi-n10/archive/