summaryrefslogtreecommitdiffstats
path: root/arch/arm/boot/dts/omap34xx-omap36xx-clocks.dtsi
diff options
context:
space:
mode:
authorTony Lindgren <tony@atomide.com>2022-04-29 08:57:36 +0200
committerTony Lindgren <tony@atomide.com>2022-05-03 08:15:42 +0200
commit4e28ab96e311e4cf07f064f3bbe78e92ef013b15 (patch)
tree808901733e5989777021e1c5f550e9f23751de69 /arch/arm/boot/dts/omap34xx-omap36xx-clocks.dtsi
parentARM: dts: Group omap3 CM_ICLKEN1_CORE clocks (diff)
downloadlinux-4e28ab96e311e4cf07f064f3bbe78e92ef013b15.tar.xz
linux-4e28ab96e311e4cf07f064f3bbe78e92ef013b15.zip
ARM: dts: Group omap3 CM_ICLKEN3_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/omap34xx-omap36xx-clocks.dtsi')
-rw-r--r--arch/arm/boot/dts/omap34xx-omap36xx-clocks.dtsi21
1 files changed, 15 insertions, 6 deletions
diff --git a/arch/arm/boot/dts/omap34xx-omap36xx-clocks.dtsi b/arch/arm/boot/dts/omap34xx-omap36xx-clocks.dtsi
index eca6b2513f41..b6316be894ce 100644
--- a/arch/arm/boot/dts/omap34xx-omap36xx-clocks.dtsi
+++ b/arch/arm/boot/dts/omap34xx-omap36xx-clocks.dtsi
@@ -231,12 +231,21 @@
ti,bit-shift = <23>;
};
};
- mad2d_ick: mad2d_ick@a18 {
- #clock-cells = <0>;
- compatible = "ti,omap3-interface-clock";
- clocks = <&l3_ick>;
- reg = <0x0a18>;
- ti,bit-shift = <3>;
+
+ /* CM_ICLKEN3_CORE */
+ clock@a18 {
+ compatible = "ti,clksel";
+ reg = <0xa18>;
+ #clock-cells = <2>;
+ #address-cells = <0>;
+
+ mad2d_ick: clock-mad2d-ick {
+ #clock-cells = <0>;
+ compatible = "ti,omap3-interface-clock";
+ clock-output-names = "mad2d_ick";
+ clocks = <&l3_ick>;
+ ti,bit-shift = <3>;
+ };
};
};