summaryrefslogtreecommitdiff
path: root/arch/arm/boot/dts/omap36xx-am35xx-omap3430es2plus-clocks.dtsi
diff options
context:
space:
mode:
authorTony Lindgren <tony@atomide.com>2022-04-29 09:57:36 +0300
committerTony Lindgren <tony@atomide.com>2022-05-03 09:15:41 +0300
commit3408a95f213e71fae8a9530872ecd2a77be78926 (patch)
treef5b9d3a50cebe7a1bb790e6595534c68fa769f3c /arch/arm/boot/dts/omap36xx-am35xx-omap3430es2plus-clocks.dtsi
parent1e7079d32e6ae9ec8caae2a4e7d9696b97307b7a (diff)
ARM: dts: Group omap3 CM_FCLKEN1_CORE clocks
The clksel related registers on omap3 cause unique_unit_address and node_name_chars_strict warnings with the W=1 or W=2 make flags enabled. With the clock drivers updated, we can now avoid most of these warnings by grouping the TI component clocks using the TI clksel binding, and with the use of clock-output-names property to avoid non-standard node names for the clocks. Signed-off-by: Tony Lindgren <tony@atomide.com>
Diffstat (limited to 'arch/arm/boot/dts/omap36xx-am35xx-omap3430es2plus-clocks.dtsi')
-rw-r--r--arch/arm/boot/dts/omap36xx-am35xx-omap3430es2plus-clocks.dtsi19
1 files changed, 13 insertions, 6 deletions
diff --git a/arch/arm/boot/dts/omap36xx-am35xx-omap3430es2plus-clocks.dtsi b/arch/arm/boot/dts/omap36xx-am35xx-omap3430es2plus-clocks.dtsi
index 9974d5226971..d698b05b742d 100644
--- a/arch/arm/boot/dts/omap36xx-am35xx-omap3430es2plus-clocks.dtsi
+++ b/arch/arm/boot/dts/omap36xx-am35xx-omap3430es2plus-clocks.dtsi
@@ -149,12 +149,19 @@
ti,bit-shift = <30>;
};
- mmchs3_fck: mmchs3_fck@a00 {
- #clock-cells = <0>;
- compatible = "ti,wait-gate-clock";
- clocks = <&core_96m_fck>;
- reg = <0x0a00>;
- ti,bit-shift = <30>;
+ clock@a00 {
+ compatible = "ti,clksel";
+ reg = <0xa00>;
+ #clock-cells = <2>;
+ #address-cells = <0>;
+
+ mmchs3_fck: clock-mmchs3-fck {
+ #clock-cells = <0>;
+ compatible = "ti,wait-gate-clock";
+ clock-output-names = "mmchs3_fck";
+ clocks = <&core_96m_fck>;
+ ti,bit-shift = <30>;
+ };
};
dss1_alwon_fck: dss1_alwon_fck_3430es2@e00 {