drop more platform data for dra7
Subsystems (5)
Tony Lindgren
maintainercover drop more platform data for dra7
Hi all,
Here are few more trivial changes to drop legacy platform data for dra7.
These are based on my omap-for-v5.4/ti-sysc-drop-pdata branch.
Regards,
Tony
Tony Lindgren (6):
ARM: OMAP2+: Drop legacy platform data for dra7 mcspi
ARM: OMAP2+: Drop legacy platform data for dra7 mcasp
ARM: dts: Drop legacy custom hwmods property for dra7 uart
ARM: dts: Drop legacy custom hwmods property for dra7 i2c
ARM: dts: Drop legacy custom hwmods property for dra7 mmc
ARM: dts: Drop legacy custom hwmods property for dra7 gpio
arch/arm/boot/dts/dra7-l4.dtsi | 39 -- arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 410 ---------------------- 2 files changed, 449 deletions(-)
Signature · 1 line
2.23.0
Tony Lindgren
maintainerPATCH 1/6 ARM: OMAP2+: Drop legacy platform data for dra7 mcspi
With recent ti-sysc driver changes, we can probe most devices with device tree data only and drop the custom "ti,hwmods" property.
Let's drop the legacy platform data and custom "ti,hwmods" property. We want to do this in a single patch as the "ti,hwmods" property is used to allocate platform data dynamically that we no longer want to do.
--- arch/arm/boot/dts/dra7-l4.dtsi | 4 - arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 116 ---------------------- 2 files changed, 120 deletions(-)
arch/arm/boot/dts/dra7-l4.dtsi +0 -4
@@ -1942,7 +1942,6 @@ target-module@98000 { /* 0x48098000, ap 47 08.0 */ compatible = "ti,sysc-omap4", "ti,sysc"; - ti,hwmods = "mcspi1"; reg = <0x98000 0x4>, <0x98010 0x4>; reg-names = "rev", "sysc";
@@ -1982,7 +1981,6 @@ target-module@9a000 { /* 0x4809a000, ap 49 10.0 */ compatible = "ti,sysc-omap4", "ti,sysc"; - ti,hwmods = "mcspi2"; reg = <0x9a000 0x4>, <0x9a010 0x4>; reg-names = "rev", "sysc";
@@ -2174,7 +2172,6 @@ target-module@b8000 { /* 0x480b8000, ap 67 48.0 */ compatible = "ti,sysc-omap4", "ti,sysc"; - ti,hwmods = "mcspi3"; reg = <0xb8000 0x4>, <0xb8010 0x4>; reg-names = "rev", "sysc";
@@ -2206,7 +2203,6 @@ target-module@ba000 { /* 0x480ba000, ap 69 18.0 */ compatible = "ti,sysc-omap4", "ti,sysc"; - ti,hwmods = "mcspi4"; reg = <0xba000 0x4>, <0xba010 0x4>; reg-names = "rev", "sysc";
arch/arm/mach-omap2/omap_hwmod_7xx_data.c +0 -116
134 lines not on this page · raw message
Signature · 1 line
2.23.0
Tony Lindgren
maintainerPATCH 2/6 ARM: OMAP2+: Drop legacy platform data for dra7 mcasp
In reply to Tony LindgrenWith recent ti-sysc driver changes, we can probe most devices with device tree data only and drop the custom "ti,hwmods" property.
Let's drop the legacy platform data and custom "ti,hwmods" property. We want to do this in a single patch as the "ti,hwmods" property is used to allocate platform data dynamically that we no longer want to do.
--- arch/arm/boot/dts/dra7-l4.dtsi | 8 - arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 294 ---------------------- 2 files changed, 302 deletions(-)
arch/arm/boot/dts/dra7-l4.dtsi +0 -8
@@ -2731,7 +2731,6 @@ target-module@60000 { /* 0x48460000, ap 9 0e.0 */ compatible = "ti,sysc-dra7-mcasp", "ti,sysc"; - ti,hwmods = "mcasp1"; reg = <0x60000 0x4>, <0x60004 0x4>; reg-names = "rev", "sysc";
@@ -2768,7 +2767,6 @@ target-module@64000 { /* 0x48464000, ap 11 1e.0 */ compatible = "ti,sysc-dra7-mcasp", "ti,sysc"; - ti,hwmods = "mcasp2"; reg = <0x64000 0x4>, <0x64004 0x4>; reg-names = "rev", "sysc";
@@ -2805,7 +2803,6 @@ target-module@68000 { /* 0x48468000, ap 13 26.0 */ compatible = "ti,sysc-dra7-mcasp", "ti,sysc"; - ti,hwmods = "mcasp3"; reg = <0x68000 0x4>, <0x68004 0x4>; reg-names = "rev", "sysc";
@@ -2841,7 +2838,6 @@ target-module@6c000 { /* 0x4846c000, ap 15 2e.0 */ compatible = "ti,sysc-dra7-mcasp", "ti,sysc"; - ti,hwmods = "mcasp4"; reg = <0x6c000 0x4>, <0x6c004 0x4>; reg-names = "rev", "sysc";
@@ -2877,7 +2873,6 @@ target-module@70000 { /* 0x48470000, ap 19 36.0 */ compatible = "ti,sysc-dra7-mcasp", "ti,sysc"; - ti,hwmods = "mcasp5"; reg = <0x70000 0x4>, <0x70004 0x4>; reg-names = "rev", "sysc";
@@ -2913,7 +2908,6 @@ target-module@74000 { /* 0x48474000, ap 35 14.0 */ compatible = "ti,sysc-dra7-mcasp", "ti,sysc"; - ti,hwmods = "mcasp6"; reg = <0x74000 0x4>, <0x74004 0x4>; reg-names = "rev", "sysc";
@@ -2949,7 +2943,6 @@ target-module@78000 { /* 0x48478000, ap 39 0c.0 */ compatible = "ti,sysc-dra7-mcasp", "ti,sysc"; - ti,hwmods = "mcasp7"; reg = <0x78000 0x4>, <0x78004 0x4>; reg-names = "rev", "sysc";
@@ -2985,7 +2978,6 @@ target-module@7c000 { /* 0x4847c000, ap 43 04.0 */ compatible = "ti,sysc-dra7-mcasp", "ti,sysc"; - ti,hwmods = "mcasp8"; reg = <0x7c000 0x4>, <0x7c004 0x4>; reg-names = "rev", "sysc";
arch/arm/mach-omap2/omap_hwmod_7xx_data.c +0 -294
312 lines not on this page · raw message
Signature · 1 line
2.23.0
Tony Lindgren
maintainerPATCH 3/6 ARM: dts: Drop legacy custom hwmods property for dra7 uart
In reply to Tony LindgrenWith recent ti-sysc driver changes, we can probe most devices with device tree data only and drop the custom "ti,hwmods" property.
We have already added the related device tree data earlier, and have already dropped the platform data. But we have been still dynamically allocating the platform data based on "ti,hwmods" property. With recent ti-sysc driver changes this is no longer needed.
--- arch/arm/boot/dts/dra7-l4.dtsi | 10 ---------- 1 file changed, 10 deletions(-)
arch/arm/boot/dts/dra7-l4.dtsi +0 -10
@@ -1118,7 +1118,6 @@ target-module@20000 { /* 0x48020000, ap 3 04.0 */ compatible = "ti,sysc-omap2", "ti,sysc"; - ti,hwmods = "uart3"; reg = <0x20050 0x4>, <0x20054 0x4>, <0x20058 0x4>;
@@ -1534,7 +1533,6 @@ target-module@66000 { /* 0x48066000, ap 63 14.0 */ compatible = "ti,sysc-omap2", "ti,sysc"; - ti,hwmods = "uart5"; reg = <0x66050 0x4>, <0x66054 0x4>, <0x66058 0x4>;
@@ -1567,7 +1565,6 @@ target-module@68000 { /* 0x48068000, ap 53 1c.0 */ compatible = "ti,sysc-omap2", "ti,sysc"; - ti,hwmods = "uart6"; reg = <0x68050 0x4>, <0x68054 0x4>, <0x68058 0x4>;
@@ -1600,7 +1597,6 @@ target-module@6a000 { /* 0x4806a000, ap 24 24.0 */ compatible = "ti,sysc-omap2", "ti,sysc"; - ti,hwmods = "uart1"; reg = <0x6a050 0x4>, <0x6a054 0x4>, <0x6a058 0x4>;
@@ -1633,7 +1629,6 @@ target-module@6c000 { /* 0x4806c000, ap 26 2c.0 */ compatible = "ti,sysc-omap2", "ti,sysc"; - ti,hwmods = "uart2"; reg = <0x6c050 0x4>, <0x6c054 0x4>, <0x6c058 0x4>;
@@ -1666,7 +1661,6 @@ target-module@6e000 { /* 0x4806e000, ap 28 0c.1 */ compatible = "ti,sysc-omap2", "ti,sysc"; - ti,hwmods = "uart4"; reg = <0x6e050 0x4>, <0x6e054 0x4>, <0x6e058 0x4>;
@@ -2380,7 +2374,6 @@ target-module@20000 { /* 0x48420000, ap 47 02.0 */ compatible = "ti,sysc-omap2", "ti,sysc"; - ti,hwmods = "uart7"; reg = <0x20050 0x4>, <0x20054 0x4>, <0x20058 0x4>;
@@ -2411,7 +2404,6 @@ target-module@22000 { /* 0x48422000, ap 49 0a.0 */ compatible = "ti,sysc-omap2", "ti,sysc"; - ti,hwmods = "uart8"; reg = <0x22050 0x4>, <0x22054 0x4>, <0x22058 0x4>;
@@ -2442,7 +2434,6 @@ target-module@24000 { /* 0x48424000, ap 51 12.0 */ compatible = "ti,sysc-omap2", "ti,sysc"; - ti,hwmods = "uart9"; reg = <0x24050 0x4>, <0x24054 0x4>, <0x24058 0x4>;
@@ -4467,7 +4458,6 @@ target-module@b000 { /* 0x4ae2b000, ap 28 02.0 */ compatible = "ti,sysc-omap2", "ti,sysc"; - ti,hwmods = "uart10"; reg = <0xb050 0x4>, <0xb054 0x4>, <0xb058 0x4>;
Signature · 1 line
2.23.0
Tony Lindgren
maintainerPATCH 4/6 ARM: dts: Drop legacy custom hwmods property for dra7 i2c
In reply to Tony LindgrenWith recent ti-sysc driver changes, we can probe most devices with device tree data only and drop the custom "ti,hwmods" property.
We have already added the related device tree data earlier, and have already dropped the platform data. But we have been still dynamically allocating the platform data based on "ti,hwmods" property. With recent ti-sysc driver changes this is no longer needed.
--- arch/arm/boot/dts/dra7-l4.dtsi | 5 ----- 1 file changed, 5 deletions(-)
arch/arm/boot/dts/dra7-l4.dtsi +0 -5
@@ -1500,7 +1500,6 @@ target-module@60000 { /* 0x48060000, ap 23 32.0 */ compatible = "ti,sysc-omap2", "ti,sysc"; - ti,hwmods = "i2c3"; reg = <0x60000 0x8>, <0x60010 0x8>, <0x60090 0x8>;
@@ -1693,7 +1692,6 @@ target-module@70000 { /* 0x48070000, ap 30 22.0 */ compatible = "ti,sysc-omap2", "ti,sysc"; - ti,hwmods = "i2c1"; reg = <0x70000 0x8>, <0x70010 0x8>, <0x70090 0x8>;
@@ -1726,7 +1724,6 @@ target-module@72000 { /* 0x48072000, ap 32 2a.0 */ compatible = "ti,sysc-omap2", "ti,sysc"; - ti,hwmods = "i2c2"; reg = <0x72000 0x8>, <0x72010 0x8>, <0x72090 0x8>;
@@ -1789,7 +1786,6 @@ target-module@7a000 { /* 0x4807a000, ap 81 3a.0 */ compatible = "ti,sysc-omap2", "ti,sysc"; - ti,hwmods = "i2c4"; reg = <0x7a000 0x8>, <0x7a010 0x8>, <0x7a090 0x8>;
@@ -1822,7 +1818,6 @@ target-module@7c000 { /* 0x4807c000, ap 83 4a.0 */ compatible = "ti,sysc-omap2", "ti,sysc"; - ti,hwmods = "i2c5"; reg = <0x7c000 0x8>, <0x7c010 0x8>, <0x7c090 0x8>;
Signature · 1 line
2.23.0
Tony Lindgren
maintainerPATCH 5/6 ARM: dts: Drop legacy custom hwmods property for dra7 mmc
In reply to Tony LindgrenWith recent ti-sysc driver changes, we can probe most devices with device tree data only and drop the custom "ti,hwmods" property.
We have already added the related device tree data earlier, and have already dropped the platform data. But we have been still dynamically allocating the platform data based on "ti,hwmods" property. With recent ti-sysc driver changes this is no longer needed.
--- arch/arm/boot/dts/dra7-l4.dtsi | 4 ---- 1 file changed, 4 deletions(-)
arch/arm/boot/dts/dra7-l4.dtsi +0 -4
@@ -2004,7 +2004,6 @@ target-module@9c000 { /* 0x4809c000, ap 51 38.0 */ compatible = "ti,sysc-omap4", "ti,sysc"; - ti,hwmods = "mmc1"; reg = <0x9c000 0x4>, <0x9c010 0x4>; reg-names = "rev", "sysc";
@@ -2064,7 +2063,6 @@ target-module@ad000 { /* 0x480ad000, ap 61 20.0 */ compatible = "ti,sysc-omap4", "ti,sysc"; - ti,hwmods = "mmc3"; reg = <0xad000 0x4>, <0xad010 0x4>; reg-names = "rev", "sysc";
@@ -2124,7 +2122,6 @@ target-module@b4000 { /* 0x480b4000, ap 65 40.0 */ compatible = "ti,sysc-omap4", "ti,sysc"; - ti,hwmods = "mmc2"; reg = <0xb4000 0x4>, <0xb4010 0x4>; reg-names = "rev", "sysc";
@@ -2223,7 +2220,6 @@ target-module@d1000 { /* 0x480d1000, ap 71 28.0 */ compatible = "ti,sysc-omap4", "ti,sysc"; - ti,hwmods = "mmc4"; reg = <0xd1000 0x4>, <0xd1010 0x4>; reg-names = "rev", "sysc";
Signature · 1 line
2.23.0
Tony Lindgren
maintainerPATCH 6/6 ARM: dts: Drop legacy custom hwmods property for dra7 gpio
In reply to Tony LindgrenWith recent ti-sysc driver changes, we can probe most devices with device tree data only and drop the custom "ti,hwmods" property.
We have already added the related device tree data earlier, and have already dropped the platform data. But we have been still dynamically allocating the platform data based on "ti,hwmods" property. With recent ti-sysc driver changes this is no longer needed.
--- arch/arm/boot/dts/dra7-l4.dtsi | 8 -------- 1 file changed, 8 deletions(-)
arch/arm/boot/dts/dra7-l4.dtsi +0 -8
@@ -1262,7 +1262,6 @@ gpio7_target: target-module@51000 { /* 0x48051000, ap 45 2e.0 */ compatible = "ti,sysc-omap2", "ti,sysc"; - ti,hwmods = "gpio7"; reg = <0x51000 0x4>, <0x51010 0x4>, <0x51114 0x4>;
@@ -1296,7 +1295,6 @@ target-module@53000 { /* 0x48053000, ap 35 36.0 */ compatible = "ti,sysc-omap2", "ti,sysc"; - ti,hwmods = "gpio8"; reg = <0x53000 0x4>, <0x53010 0x4>, <0x53114 0x4>;
@@ -1330,7 +1328,6 @@ target-module@55000 { /* 0x48055000, ap 13 0e.0 */ compatible = "ti,sysc-omap2", "ti,sysc"; - ti,hwmods = "gpio2"; reg = <0x55000 0x4>, <0x55010 0x4>, <0x55114 0x4>;
@@ -1364,7 +1361,6 @@ target-module@57000 { /* 0x48057000, ap 15 06.0 */ compatible = "ti,sysc-omap2", "ti,sysc"; - ti,hwmods = "gpio3"; reg = <0x57000 0x4>, <0x57010 0x4>, <0x57114 0x4>;
@@ -1398,7 +1394,6 @@ target-module@59000 { /* 0x48059000, ap 17 16.0 */ compatible = "ti,sysc-omap2", "ti,sysc"; - ti,hwmods = "gpio4"; reg = <0x59000 0x4>, <0x59010 0x4>, <0x59114 0x4>;
@@ -1432,7 +1427,6 @@ target-module@5b000 { /* 0x4805b000, ap 19 1e.0 */ compatible = "ti,sysc-omap2", "ti,sysc"; - ti,hwmods = "gpio5"; reg = <0x5b000 0x4>, <0x5b010 0x4>, <0x5b114 0x4>;
@@ -1466,7 +1460,6 @@ target-module@5d000 { /* 0x4805d000, ap 21 26.0 */ compatible = "ti,sysc-omap2", "ti,sysc"; - ti,hwmods = "gpio6"; reg = <0x5d000 0x4>, <0x5d010 0x4>, <0x5d114 0x4>;
@@ -4281,7 +4274,6 @@ target-module@0 { /* 0x4ae10000, ap 5 20.0 */ compatible = "ti,sysc-omap2", "ti,sysc"; - ti,hwmods = "gpio1"; reg = <0x0 0x4>, <0x10 0x4>, <0x114 0x4>;
Signature · 1 line
2.23.0