The specific partition mapping definitively belongs to a rt305x-eval.dts
file and not a dtsi you would create.
I’ll split this into 2 files
+};
diff --git a/arch/mips/ralink/rt305x.c b/arch/mips/ralink/rt305x.c
index 1e24439..f4b2e4d 100644
--- a/arch/mips/ralink/rt305x.c
+++ b/arch/mips/ralink/rt305x.c
@@ -185,8 +185,8 @@ void __init ralink_clk_init(void)
void __init ralink_of_remap(void)
{
- rt_sysc_membase = plat_of_remap_node("ralink,rt305x-sysc");
- rt_memc_membase = plat_of_remap_node("ralink,rt305x-memc");
+ rt_sysc_membase = plat_of_remap_node("ralink,rt3052-sysc");
+ rt_memc_membase = plat_of_remap_node("ralink,rt3052-memc");
Why are you doing this? If you specify multiple compatible properties,
such as:
compatible = "ralink,rt3052-sysc", "ralink,rt305x-sysc" you should be
good in any case no?
I folded that fix into the wrong patch :-)
using wild cards is discouraged for compatible strings rt3052 was the
first silicon with this sysc version.
John
