[PATCH] arm64: dts: realtek: Fix memory node unit-address mismatch

Yu-Chun Lin posted 1 patch 2 weeks, 5 days ago
arch/arm64/boot/dts/realtek/rtd1501s-phantom-8gb.dts    | 2 +-
arch/arm64/boot/dts/realtek/rtd1861b-krypton-8gb.dts    | 2 +-
arch/arm64/boot/dts/realtek/rtd1920s-smallville-4gb.dts | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
[PATCH] arm64: dts: realtek: Fix memory node unit-address mismatch
Posted by Yu-Chun Lin 2 weeks, 5 days ago
The memory node unit-address should match the first address in the reg
property. Correct the unit-address from @40000 to @50000 to align with the
actual base address (0x50000) defined in the reg property.

Fixes: b095c27fc874 ("arm64: dts: realtek: Add Kent SoC and EVB device trees")
Signed-off-by: Yu-Chun Lin <eleanor.lin@realtek.com>
---
This patch series is sent to both Realtek and ARM SoC maintainers.
While Andreas Färber is listed as the Realtek maintainer, there has been
limited activity recently.
---
 arch/arm64/boot/dts/realtek/rtd1501s-phantom-8gb.dts    | 2 +-
 arch/arm64/boot/dts/realtek/rtd1861b-krypton-8gb.dts    | 2 +-
 arch/arm64/boot/dts/realtek/rtd1920s-smallville-4gb.dts | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/arch/arm64/boot/dts/realtek/rtd1501s-phantom-8gb.dts b/arch/arm64/boot/dts/realtek/rtd1501s-phantom-8gb.dts
index 09e544acfd34..e487622424f1 100644
--- a/arch/arm64/boot/dts/realtek/rtd1501s-phantom-8gb.dts
+++ b/arch/arm64/boot/dts/realtek/rtd1501s-phantom-8gb.dts
@@ -13,7 +13,7 @@ / {
 	compatible = "realtek,phantom", "realtek,rtd1501s";
 	model = "Realtek Phantom EVB Chromium (8GB)";
 
-	memory@40000 {
+	memory@50000 {
 		device_type = "memory";
 		reg = <0x0 0x50000 0x0 0x7ffb0000>,
 		      <0x0 0x8a100000 0x0 0xdef0000>,
diff --git a/arch/arm64/boot/dts/realtek/rtd1861b-krypton-8gb.dts b/arch/arm64/boot/dts/realtek/rtd1861b-krypton-8gb.dts
index 9c23d901c49c..f0f810ab8aa8 100644
--- a/arch/arm64/boot/dts/realtek/rtd1861b-krypton-8gb.dts
+++ b/arch/arm64/boot/dts/realtek/rtd1861b-krypton-8gb.dts
@@ -13,7 +13,7 @@ / {
 	compatible = "realtek,krypton", "realtek,rtd1861b";
 	model = "Realtek Krypton EVB (8GB)";
 
-	memory@40000 {
+	memory@50000 {
 		device_type = "memory";
 		reg = <0x0 0x50000 0x0 0x7ffb0000>,
 		      <0x0 0x8a100000 0x0 0xdef0000>,
diff --git a/arch/arm64/boot/dts/realtek/rtd1920s-smallville-4gb.dts b/arch/arm64/boot/dts/realtek/rtd1920s-smallville-4gb.dts
index 9fd6976e0d9b..375c18322c3b 100644
--- a/arch/arm64/boot/dts/realtek/rtd1920s-smallville-4gb.dts
+++ b/arch/arm64/boot/dts/realtek/rtd1920s-smallville-4gb.dts
@@ -13,7 +13,7 @@ / {
 	compatible = "realtek,smallville", "realtek,rtd1920s";
 	model = "Realtek Smallville EVB (4GB)";
 
-	memory@40000 {
+	memory@50000 {
 		device_type = "memory";
 		reg = <0x0 0x50000 0x0 0x7ffb0000>,
 		      <0x0 0x8a100000 0x0 0xdef0000>,
-- 
2.34.1

Re: [PATCH] arm64: dts: realtek: Fix memory node unit-address mismatch
Posted by Krzysztof Kozlowski 2 weeks, 5 days ago
On 18/03/2026 12:40, Yu-Chun Lin wrote:
> The memory node unit-address should match the first address in the reg
> property. Correct the unit-address from @40000 to @50000 to align with the
> actual base address (0x50000) defined in the reg property.
> 
> Fixes: b095c27fc874 ("arm64: dts: realtek: Add Kent SoC and EVB device trees")
> Signed-off-by: Yu-Chun Lin <eleanor.lin@realtek.com>
> ---
> This patch series is sent to both Realtek and ARM SoC maintainers.
> While Andreas Färber is listed as the Realtek maintainer, there has been
> limited activity recently.

Unfortunately nothing new, likely two years ago I was also complaining
on lack of maintenance on Realtek, but the solution is not to send
patches to soc@.

Solution to that would be to remove the platform, for example. Or work
on maintainership.

Did anyone from Realtek offered reviews to my patches posted 3 and 2
years ago? I don't see that.

Kent SoC was accepted under condition this will improve.

I drop this from soc patchwork and please do not send code for review
there, but either fix the lack of involvement from Realtek or let's drop
the platform if Realtek does not care.

Best regards,
Krzysztof