Remove ethernetX aliases from the SoC dtsi for RK3399, RK3368, RK3328 and PX30
Subsystems (2)
cover Remove ethernetX aliases from the SoC dtsi for RK3399, RK3368, RK3328 and PX30
Unlike for the I2C buses, GPIO lines and UARTs, the Rockchip SoC TRMs and datasheets define no numbering for the built-in GMAC(s) or MAC(s), if there are more than one found in the particular Rockchip SoC.
Moreover, not all boards or devices based on these SoCs actually use the built-in GMAC(s) or MAC(s). Thus, let's remove the ethernetX aliases from the SoC dtsi files and add them back to the appropriate board and device dts(i) files. See also [1] for the initial discussion.
This is quite similar to the already performed migration of the mmcX aliases from the Rockchip SoC dtsi files to the board dts(i) files.
The correctness of the patches in this series was verified by comparing the contents of the compiled dtb files before and after applying the patches. All of the affected dtb files checked out fine.
[1] https://lore.kernel.org/linux-rockchip/5119280.687JKscXgg@diego/T/#u
Dragan Simic (4):
arm64: dts: rockchip: Remove ethernet0 alias from the SoC dtsi for
RK3399
arm64: dts: rockchip: Remove ethernet0 alias from the SoC dtsi for
RK3368
arm64: dts: rockchip: Remove ethernetX aliases from the SoC dtsi for
RK3328
arm64: dts: rockchip: Remove ethernet0 alias from the SoC dtsi for
PX30arch/arm64/boot/dts/rockchip/px30-engicam-common.dtsi | 1 + arch/arm64/boot/dts/rockchip/px30-evb.dts | 1 + arch/arm64/boot/dts/rockchip/px30-ringneck-haikou.dts | 1 + arch/arm64/boot/dts/rockchip/px30.dtsi | 1 - arch/arm64/boot/dts/rockchip/rk3318-a95x-z2.dts | 1 + arch/arm64/boot/dts/rockchip/rk3328-a1.dts | 1 + arch/arm64/boot/dts/rockchip/rk3328-evb.dts | 1 + arch/arm64/boot/dts/rockchip/rk3328-nanopi-r2s.dts | 1 + arch/arm64/boot/dts/rockchip/rk3328-orangepi-r1-plus.dts | 1 + arch/arm64/boot/dts/rockchip/rk3328-roc-cc.dts | 1 + arch/arm64/boot/dts/rockchip/rk3328-rock-pi-e.dts | 2 ++ arch/arm64/boot/dts/rockchip/rk3328-rock64.dts | 1 + arch/arm64/boot/dts/rockchip/rk3328.dtsi | 2 -- arch/arm64/boot/dts/rockchip/rk3368-evb.dtsi | 1 + arch/arm64/boot/dts/rockchip/rk3368-geekbox.dts | 1 + arch/arm64/boot/dts/rockchip/rk3368-lion.dtsi | 1 + arch/arm64/boot/dts/rockchip/rk3368-orion-r68-meta.dts | 1 + arch/arm64/boot/dts/rockchip/rk3368-r88.dts | 1 + arch/arm64/boot/dts/rockchip/rk3368.dtsi | 1 - arch/arm64/boot/dts/rockchip/rk3399-eaidk-610.dts | 1 + arch/arm64/boot/dts/rockchip/rk3399-evb.dts | 1 + arch/arm64/boot/dts/rockchip/rk3399-ficus.dts | 4 ++++ arch/arm64/boot/dts/rockchip/rk3399-firefly.dts | 1 + arch/arm64/boot/dts/rockchip/rk3399-hugsun-x99.dts | 1 + arch/arm64/boot/dts/rockchip/rk3399-khadas-edge-captain.dts | 4 ++++ arch/arm64/boot/dts/rockchip/rk3399-khadas-edge-v.dts | 4 ++++ arch/arm64/boot/dts/rockchip/rk3399-kobol-helios64.dts | 1 + arch/arm64/boot/dts/rockchip/rk3399-leez-p710.dts | 1 + arch/arm64/boot/dts/rockchip/rk3399-nanopi4.dtsi | 1 + arch/arm64/boot/dts/rockchip/rk3399-orangepi.dts | 1 + arch/arm64/boot/dts/rockchip/rk3399-puma.dtsi | 1 + arch/arm64/boot/dts/rockchip/rk3399-roc-pc.dtsi | 1 + arch/arm64/boot/dts/rockchip/rk3399-rock-4c-plus.dts | 1 + arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4.dtsi | 1 + arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dtsi | 1 + arch/arm64/boot/dts/rockchip/rk3399-sapphire.dtsi | 1 + arch/arm64/boot/dts/rockchip/rk3399.dtsi | 1 - arch/arm64/boot/dts/rockchip/rk3399pro-vmarc-som.dtsi | 1 + 38 files changed, 44 insertions(+), 5 deletions(-)
PATCH 1/4 arm64: dts: rockchip: Remove ethernet0 alias from the SoC dtsi for RK3399
Not all supported boards actually use the RK3399's built-in GMAC, while the SoC TRM and the datasheet don't define some standard numbering in this case. Thus, remove the ethernet0 alias from the RK3399 SoC dtsi file, and add the same alias back to the appropriate board dts(i) files.
This is quite similar to the already performed migration of the mmcX aliases from the Rockchip SoC dtsi files to the board dts(i) files.
--- arch/arm64/boot/dts/rockchip/rk3399-eaidk-610.dts | 1 + arch/arm64/boot/dts/rockchip/rk3399-evb.dts | 1 + arch/arm64/boot/dts/rockchip/rk3399-ficus.dts | 4 ++++ arch/arm64/boot/dts/rockchip/rk3399-firefly.dts | 1 + arch/arm64/boot/dts/rockchip/rk3399-hugsun-x99.dts | 1 + arch/arm64/boot/dts/rockchip/rk3399-khadas-edge-captain.dts | 4 ++++ arch/arm64/boot/dts/rockchip/rk3399-khadas-edge-v.dts | 4 ++++ arch/arm64/boot/dts/rockchip/rk3399-kobol-helios64.dts | 1 + arch/arm64/boot/dts/rockchip/rk3399-leez-p710.dts | 1 + arch/arm64/boot/dts/rockchip/rk3399-nanopi4.dtsi | 1 + arch/arm64/boot/dts/rockchip/rk3399-orangepi.dts | 1 + arch/arm64/boot/dts/rockchip/rk3399-puma.dtsi | 1 + arch/arm64/boot/dts/rockchip/rk3399-roc-pc.dtsi | 1 + arch/arm64/boot/dts/rockchip/rk3399-rock-4c-plus.dts | 1 + arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4.dtsi | 1 + arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dtsi | 1 + arch/arm64/boot/dts/rockchip/rk3399-sapphire.dtsi | 1 + arch/arm64/boot/dts/rockchip/rk3399.dtsi | 1 - arch/arm64/boot/dts/rockchip/rk3399pro-vmarc-som.dtsi | 1 + 19 files changed, 27 insertions(+), 1 deletion(-)
arch/arm64/boot/dts/rockchip/rk3399-eaidk-610.dts +1 -0
@@ -15,6 +15,7 @@ / { compatible = "openailab,eaidk-610", "rockchip,rk3399"; aliases { + ethernet0 = &gmac; mmc0 = &sdio0; mmc1 = &sdmmc; mmc2 = &sdhci;
arch/arm64/boot/dts/rockchip/rk3399-evb.dts +1 -0
@@ -12,6 +12,7 @@ / { compatible = "rockchip,rk3399-evb", "rockchip,rk3399"; aliases { + ethernet0 = &gmac; mmc0 = &sdhci; };
arch/arm64/boot/dts/rockchip/rk3399-ficus.dts +4 -0
@@ -13,6 +13,10 @@ / { model = "96boards RK3399 Ficus"; compatible = "vamrs,ficus", "rockchip,rk3399"; + aliases { + ethernet0 = &gmac; + }; + chosen { stdout-path = "serial2:1500000n8"; };
arch/arm64/boot/dts/rockchip/rk3399-firefly.dts +1 -0
@@ -16,6 +16,7 @@ / { compatible = "firefly,firefly-rk3399", "rockchip,rk3399"; aliases { + ethernet0 = &gmac; mmc0 = &sdio0; mmc1 = &sdmmc; mmc2 = &sdhci;
arch/arm64/boot/dts/rockchip/rk3399-hugsun-x99.dts +1 -0
@@ -11,6 +11,7 @@ / { compatible = "hugsun,x99", "rockchip,rk3399"; aliases { + ethernet0 = &gmac; mmc0 = &sdio0; mmc1 = &sdmmc; mmc2 = &sdhci;
arch/arm64/boot/dts/rockchip/rk3399-khadas-edge-captain.dts +4 -0
@@ -10,6 +10,10 @@ / { model = "Khadas Edge-Captain"; compatible = "khadas,edge-captain", "rockchip,rk3399"; + + aliases { + ethernet0 = &gmac; + }; }; &gmac {
arch/arm64/boot/dts/rockchip/rk3399-khadas-edge-v.dts +4 -0
@@ -10,6 +10,10 @@ / { model = "Khadas Edge-V"; compatible = "khadas,edge-v", "rockchip,rk3399"; + + aliases { + ethernet0 = &gmac; + }; }; &gmac {
arch/arm64/boot/dts/rockchip/rk3399-kobol-helios64.dts +1 -0
@@ -19,6 +19,7 @@ / { compatible = "kobol,helios64", "rockchip,rk3399"; aliases { + ethernet0 = &gmac; mmc0 = &sdmmc; mmc1 = &sdhci; spi1 = &spi1;
arch/arm64/boot/dts/rockchip/rk3399-leez-p710.dts +1 -0
@@ -15,6 +15,7 @@ / { compatible = "leez,p710", "rockchip,rk3399"; aliases { + ethernet0 = &gmac; mmc0 = &sdio0; mmc1 = &sdmmc; mmc2 = &sdhci;
arch/arm64/boot/dts/rockchip/rk3399-nanopi4.dtsi +1 -0
@@ -18,6 +18,7 @@ / { aliases { + ethernet0 = &gmac; mmc0 = &sdio0; mmc1 = &sdmmc; mmc2 = &sdhci;
arch/arm64/boot/dts/rockchip/rk3399-orangepi.dts +1 -0
@@ -17,6 +17,7 @@ / { compatible = "rockchip,rk3399-orangepi", "rockchip,rk3399"; aliases { + ethernet0 = &gmac; mmc0 = &sdio0; mmc1 = &sdmmc; mmc2 = &sdhci;
arch/arm64/boot/dts/rockchip/rk3399-puma.dtsi +1 -0
@@ -9,6 +9,7 @@ / { aliases { + ethernet0 = &gmac; mmc0 = &sdhci; };
arch/arm64/boot/dts/rockchip/rk3399-roc-pc.dtsi +1 -0
@@ -14,6 +14,7 @@ / { compatible = "firefly,roc-rk3399-pc", "rockchip,rk3399"; aliases { + ethernet0 = &gmac; mmc0 = &sdmmc; mmc1 = &sdhci; };
arch/arm64/boot/dts/rockchip/rk3399-rock-4c-plus.dts +1 -0
@@ -15,6 +15,7 @@ / { compatible = "radxa,rock-4c-plus", "rockchip,rk3399"; aliases { + ethernet0 = &gmac; mmc0 = &sdhci; mmc1 = &sdmmc; };
arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4.dtsi +1 -0
@@ -12,6 +12,7 @@ / { aliases { + ethernet0 = &gmac; mmc0 = &sdhci; mmc1 = &sdmmc; };
arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dtsi +1 -0
@@ -11,6 +11,7 @@ / { aliases { + ethernet0 = &gmac; mmc0 = &sdio0; mmc1 = &sdmmc; mmc2 = &sdhci;
arch/arm64/boot/dts/rockchip/rk3399-sapphire.dtsi +1 -0
@@ -12,6 +12,7 @@ / { compatible = "rockchip,rk3399-sapphire", "rockchip,rk3399"; aliases { + ethernet0 = &gmac; mmc0 = &sdmmc; mmc1 = &sdhci; };
arch/arm64/boot/dts/rockchip/rk3399.dtsi +0 -1
@@ -19,7 +19,6 @@ / { #size-cells = <2>; aliases { - ethernet0 = &gmac; i2c0 = &i2c0; i2c1 = &i2c1; i2c2 = &i2c2;
arch/arm64/boot/dts/rockchip/rk3399pro-vmarc-som.dtsi +1 -0
@@ -13,6 +13,7 @@ / { compatible = "vamrs,rk3399pro-vmarc-som", "rockchip,rk3399pro"; aliases { + ethernet0 = &gmac; mmc0 = &sdhci; mmc1 = &sdmmc; };
PATCH 2/4 arm64: dts: rockchip: Remove ethernet0 alias from the SoC dtsi for RK3368
In reply to Dragan SimicNot all supported boards actually use the RK3368's built-in GMAC, while the SoC TRM and the datasheet don't define some standard numbering in this case. Thus, remove the ethernet0 alias from the RK3368 SoC dtsi file, and add the same alias back to the appropriate board dts(i) files.
This is quite similar to the already performed migration of the mmcX aliases from the Rockchip SoC dtsi files to the board dts(i) files.
--- arch/arm64/boot/dts/rockchip/rk3368-evb.dtsi | 1 + arch/arm64/boot/dts/rockchip/rk3368-geekbox.dts | 1 + arch/arm64/boot/dts/rockchip/rk3368-lion.dtsi | 1 + arch/arm64/boot/dts/rockchip/rk3368-orion-r68-meta.dts | 1 + arch/arm64/boot/dts/rockchip/rk3368-r88.dts | 1 + arch/arm64/boot/dts/rockchip/rk3368.dtsi | 1 - 6 files changed, 5 insertions(+), 1 deletion(-)
arch/arm64/boot/dts/rockchip/rk3368-evb.dtsi +1 -0
@@ -9,6 +9,7 @@ / { aliases { + ethernet0 = &gmac; mmc0 = &emmc; };
arch/arm64/boot/dts/rockchip/rk3368-geekbox.dts +1 -0
@@ -12,6 +12,7 @@ / { compatible = "geekbuying,geekbox", "rockchip,rk3368"; aliases { + ethernet0 = &gmac; mmc0 = &emmc; };
arch/arm64/boot/dts/rockchip/rk3368-lion.dtsi +1 -0
@@ -8,6 +8,7 @@ / { aliases { + ethernet0 = &gmac; mmc0 = &emmc; };
arch/arm64/boot/dts/rockchip/rk3368-orion-r68-meta.dts +1 -0
@@ -12,6 +12,7 @@ / { compatible = "tronsmart,orion-r68-meta", "rockchip,rk3368"; aliases { + ethernet0 = &gmac; mmc0 = &sdmmc; mmc1 = &emmc; };
arch/arm64/boot/dts/rockchip/rk3368-r88.dts +1 -0
@@ -12,6 +12,7 @@ / { compatible = "rockchip,r88", "rockchip,rk3368"; aliases { + ethernet0 = &gmac; mmc0 = &sdio0; mmc1 = &emmc; };
arch/arm64/boot/dts/rockchip/rk3368.dtsi +0 -1
@@ -19,7 +19,6 @@ / { #size-cells = <2>; aliases { - ethernet0 = &gmac; i2c0 = &i2c0; i2c1 = &i2c1; i2c2 = &i2c2;
PATCH 3/4 arm64: dts: rockchip: Remove ethernetX aliases from the SoC dtsi for RK3328
In reply to Dragan SimicNot all supported boards actually use the RK3328's built-in GMACs, while the SoC TRM and the datasheet don't define some standard numbering in this case. Thus, remove the ethernet0 and ethernet1 aliases from the RK3328 SoC dtsi file, and add the same alias back to the appropriate board dts(i) files.
These changes also touch one RK3318-based board dts, because it actually depends on the RK3328 SoC dtsi and enables one of the GMACs.
This is quite similar to the already performed migration of the mmcX aliases from the Rockchip SoC dtsi files to the board dts(i) files.
--- arch/arm64/boot/dts/rockchip/rk3318-a95x-z2.dts | 1 + arch/arm64/boot/dts/rockchip/rk3328-a1.dts | 1 + arch/arm64/boot/dts/rockchip/rk3328-evb.dts | 1 + arch/arm64/boot/dts/rockchip/rk3328-nanopi-r2s.dts | 1 + arch/arm64/boot/dts/rockchip/rk3328-orangepi-r1-plus.dts | 1 + arch/arm64/boot/dts/rockchip/rk3328-roc-cc.dts | 1 + arch/arm64/boot/dts/rockchip/rk3328-rock-pi-e.dts | 2 ++ arch/arm64/boot/dts/rockchip/rk3328-rock64.dts | 1 + arch/arm64/boot/dts/rockchip/rk3328.dtsi | 2 -- 9 files changed, 9 insertions(+), 2 deletions(-)
arch/arm64/boot/dts/rockchip/rk3318-a95x-z2.dts +1 -0
@@ -9,6 +9,7 @@ / { compatible = "zkmagic,a95x-z2", "rockchip,rk3318"; aliases { + ethernet0 = &gmac2phy; mmc0 = &sdmmc; mmc1 = &sdio; mmc2 = &emmc;
arch/arm64/boot/dts/rockchip/rk3328-a1.dts +1 -0
@@ -9,6 +9,7 @@ / { compatible = "azw,beelink-a1", "rockchip,rk3328"; aliases { + ethernet0 = &gmac2io; mmc0 = &sdmmc; mmc1 = &emmc; };
arch/arm64/boot/dts/rockchip/rk3328-evb.dts +1 -0
@@ -11,6 +11,7 @@ / { compatible = "rockchip,rk3328-evb", "rockchip,rk3328"; aliases { + ethernet0 = &gmac2phy; mmc0 = &sdmmc; mmc1 = &sdio; mmc2 = &emmc;
arch/arm64/boot/dts/rockchip/rk3328-nanopi-r2s.dts +1 -0
@@ -14,6 +14,7 @@ / { compatible = "friendlyarm,nanopi-r2s", "rockchip,rk3328"; aliases { + ethernet0 = &gmac2io; ethernet1 = &rtl8153; mmc0 = &sdmmc; };
arch/arm64/boot/dts/rockchip/rk3328-orangepi-r1-plus.dts +1 -0
@@ -15,6 +15,7 @@ / { compatible = "xunlong,orangepi-r1-plus", "rockchip,rk3328"; aliases { + ethernet0 = &gmac2io; ethernet1 = &rtl8153; mmc0 = &sdmmc; };
arch/arm64/boot/dts/rockchip/rk3328-roc-cc.dts +1 -0
@@ -11,6 +11,7 @@ / { compatible = "firefly,roc-rk3328-cc", "rockchip,rk3328"; aliases { + ethernet0 = &gmac2io; mmc0 = &sdmmc; mmc1 = &emmc; };
arch/arm64/boot/dts/rockchip/rk3328-rock-pi-e.dts +2 -0
@@ -21,6 +21,8 @@ / { compatible = "radxa,rockpi-e", "rockchip,rk3328"; aliases { + ethernet0 = &gmac2io; + ethernet1 = &gmac2phy; mmc0 = &sdmmc; mmc1 = &emmc; };
arch/arm64/boot/dts/rockchip/rk3328-rock64.dts +1 -0
@@ -11,6 +11,7 @@ / { compatible = "pine64,rock64", "rockchip,rk3328"; aliases { + ethernet0 = &gmac2io; mmc0 = &sdmmc; mmc1 = &emmc; };
arch/arm64/boot/dts/rockchip/rk3328.dtsi +0 -2
@@ -27,8 +27,6 @@ aliases { i2c1 = &i2c1; i2c2 = &i2c2; i2c3 = &i2c3; - ethernet0 = &gmac2io; - ethernet1 = &gmac2phy; }; cpus {
PATCH 4/4 arm64: dts: rockchip: Remove ethernet0 alias from the SoC dtsi for PX30
In reply to Dragan SimicNot all supported boards actually use the PX30's built-in (G)MAC, while the SoC TRM and the datasheet don't define some standard numbering in this case. Thus, remove the ethernet0 alias from the PX30 SoC dtsi file, and add the same alias back to the appropriate board dts(i) files.
This is quite similar to the already performed migration of the mmcX aliases from the Rockchip SoC dtsi files to the board dts(i) files.
--- arch/arm64/boot/dts/rockchip/px30-engicam-common.dtsi | 1 + arch/arm64/boot/dts/rockchip/px30-evb.dts | 1 + arch/arm64/boot/dts/rockchip/px30-ringneck-haikou.dts | 1 + arch/arm64/boot/dts/rockchip/px30.dtsi | 1 - 4 files changed, 3 insertions(+), 1 deletion(-)
arch/arm64/boot/dts/rockchip/px30-engicam-common.dtsi +1 -0
@@ -7,6 +7,7 @@ / { aliases { + ethernet0 = &gmac; mmc1 = &sdmmc; mmc2 = &sdio; };
arch/arm64/boot/dts/rockchip/px30-evb.dts +1 -0
@@ -14,6 +14,7 @@ / { compatible = "rockchip,px30-evb", "rockchip,px30"; aliases { + ethernet0 = &gmac; mmc0 = &sdmmc; mmc1 = &sdio; mmc2 = &emmc;
arch/arm64/boot/dts/rockchip/px30-ringneck-haikou.dts +1 -0
@@ -13,6 +13,7 @@ / { compatible = "tsd,px30-ringneck-haikou", "rockchip,px30"; aliases { + ethernet0 = &gmac; mmc2 = &sdmmc; };
arch/arm64/boot/dts/rockchip/px30.dtsi +0 -1
@@ -20,7 +20,6 @@ / { #size-cells = <2>; aliases { - ethernet0 = &gmac; i2c0 = &i2c0; i2c1 = &i2c1; i2c2 = &i2c2;
Quoted 10 lines · Dragan Simic
Unlike for the I2C buses, GPIO lines and UARTs, the Rockchip SoC TRMs and datasheets define no numbering for the built-in GMAC(s) or MAC(s), if there are more than one found in the particular Rockchip SoC.
Moreover, not all boards or devices based on these SoCs actually use the built-in GMAC(s) or MAC(s). Thus, let's remove the ethernetX aliases from the SoC dtsi files and add them back to the appropriate board and device dts(i) files. See also [1] for the initial discussion.
[...]
Applied, thanks!
[1/4] arm64: dts: rockchip: Remove ethernet0 alias from the SoC dtsi for RK3399
commit: 8030063ca9b019f9dfb90a654f557d8bb15a97a5
[2/4] arm64: dts: rockchip: Remove ethernet0 alias from the SoC dtsi for RK3368
commit: 7aab60df473c70f74880267500884b12151b160b
[3/4] arm64: dts: rockchip: Remove ethernetX aliases from the SoC dtsi for RK3328
commit: 20a9a7667af6b11b7369073d0186d9c92e52db04
[4/4] arm64: dts: rockchip: Remove ethernet0 alias from the SoC dtsi for PX30
commit: a69907a915e4c15bf7e632cd324ec5c3e38c3afcBest regards,
Signature · 1 line
Heiko Stuebner <[email protected]>
Quoted 15 lines · Heiko Stuebner
Quoted 10 lines · Dragan Simic
Unlike for the I2C buses, GPIO lines and UARTs, the Rockchip SoC TRMs and datasheets define no numbering for the built-in GMAC(s) or MAC(s), if there are more than one found in the particular Rockchip SoC.
Moreover, not all boards or devices based on these SoCs actually use the built-in GMAC(s) or MAC(s). Thus, let's remove the ethernetX aliases from the SoC dtsi files and add them back to the appropriate board and device dts(i) files. See also [1] for the initial discussion.
[...]
Applied, thanks!
[1/4] arm64: dts: rockchip: Remove ethernet0 alias from the SoC dtsi for RK3399
Quoted 8 lines
commit: 8030063ca9b019f9dfb90a654f557d8bb15a97a5
[2/4] arm64: dts: rockchip: Remove ethernet0 alias from the SoC dtsi for RK3368
commit: 7aab60df473c70f74880267500884b12151b160b
[3/4] arm64: dts: rockchip: Remove ethernetX aliases from the SoC dtsi
for RK3328
commit: 20a9a7667af6b11b7369073d0186d9c92e52db04
[4/4] arm64: dts: rockchip: Remove ethernet0 alias from the SoC dtsi for PX30
commit: a69907a915e4c15bf7e632cd324ec5c3e38c3afcGreat, thanks!