Skip to contentSkip to conversation

dt-bindings: clock: ti,clockdomain: Convert to DT schema

PATCH Applied Bhargav Joshi 2 participants 2 messages Aug 10 – Aug 14

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH v4 1/1 dt-bindings: clock: ti,clockdomain: Convert to DT schema

Convert TI clockdomain to yaml DT schema. Drop '#clock-cells' from the required list as this binding doesn't define a new clock binding type, it is used to group existing clock nodes under hardware hierarchy. Most existing dts omit '#clock-cells'.

Update the reference to the old legacy text binding in the description of bindings/clock/ti/ti,gate-clock.yaml to point to the new YAML file.

---
Changes in v4:
- Rebased to Latest mainline
- Link to v3: https://lore.kernel.org/r/[email protected]

Changes in v3:
- set limits for clock-output-names and clocks properties
- Link to v2: https://lore.kernel.org/r/[email protected]

Changes in v2:
- updating the stale reference to the legacy .txt file inside bindings/clock/ti/ti,gate-clock.yaml to fix make refcheckdocs error
- Link to v1: https://lore.kernel.org/r/[email protected]

---
 .../devicetree/bindings/clock/ti/clockdomain.txt   | 25 ------------
 .../bindings/clock/ti/ti,clockdomain.yaml          | 44 ++++++++++++++++++++++
 .../bindings/clock/ti/ti,gate-clock.yaml           |  2 +-
 3 files changed, 45 insertions(+), 26 deletions(-)
Documentation/devicetree/bindings/clock/ti/clockdomain.txt deleted +0 -25
deleted file mode 100644
index edf0b5d42768..000000000000
@@ -1,25 +0,0 @@
-Binding for Texas Instruments clockdomain.
-
-This binding uses the common clock binding[1] in consumer role.
-Every clock on TI SoC belongs to one clockdomain, but software
-only needs this information for specific clocks which require
-their parent clockdomain to be controlled when the clock is
-enabled/disabled. This binding doesn't define a new clock
-binding type, it is used to group existing clock nodes under
-hardware hierarchy.
-
-[1] Documentation/devicetree/bindings/clock/clock-bindings.txt
-
-Required properties:
-- compatible : shall be "ti,clockdomain"
-- #clock-cells : from common clock binding; shall be set to 0.
-- clocks : link phandles of clocks within this domain
-
-Optional properties:
-- clock-output-names : from common clock binding.
-
-Examples:
-	dss_clkdm: dss_clkdm {
-		compatible = "ti,clockdomain";
-		clocks = <&dss1_alwon_fck_3430es2>, <&dss_ick_3430es2>;
-	};
Documentation/devicetree/bindings/clock/ti/ti,clockdomain.yaml new file +44 -0

44 lines not on this page · raw message

Documentation/devicetree/bindings/clock/ti/ti,gate-clock.yaml +1 -1
index eaa727ab0d7f..438e190d1067 100644
@@ -19,7 +19,7 @@ description: |
   that is used.
 
   [1] Documentation/devicetree/bindings/clock/gpio-gate-clock.yaml
-  [2] Documentation/devicetree/bindings/clock/ti/clockdomain.txt
+  [2] Documentation/devicetree/bindings/clock/ti/ti,clockdomain.yaml
 
 properties:
   compatible:

---
base-commit: d58772d8520c7ef247c4b95c9bd76d3a25da9ff5
change-id: 20260610-ti-clockdomain-a27dd0fa1ad5

Best regards,

Signature · 1 line
Bhargav
maintainer Applied
#1 lore raw

Quoting Bhargav Joshi (2026-08-10 11:54:59)

Quoted 11 lines

Convert TI clockdomain to yaml DT schema. Drop '#clock-cells' from the required list as this binding doesn't define a new clock binding type, it is used to group existing clock nodes under hardware hierarchy. Most existing dts omit '#clock-cells'.

Update the reference to the old legacy text binding in the description of bindings/clock/ti/ti,gate-clock.yaml to point to the new YAML file.

---

Applied to clk-next