From: Jan Kiszka <jan.kiszka@siemens.com>
Expand bindings to cover both the MCU and the main usage of the AM654
system controller.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
.../soc/ti/ti,am654-system-controller.yaml | 29 +++++++++++++++++++
1 file changed, 29 insertions(+)
diff --git a/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml b/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml
index e79803e586ca..0eec807f38df 100644
--- a/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml
+++ b/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml
@@ -34,6 +34,35 @@ patternProperties:
type: object
$ref: /schemas/phy/ti,phy-gmii-sel.yaml#
+ "^mux-controller$":
+ type: object
+ description:
+ This is the SERDES lane control mux.
+
+ "^clock@[0-9a-f]+$":
+ type: object
+ $ref: /schemas/mfd/syscon.yaml#
+ properties:
+ compatible:
+ items:
+ - const: ti,am654-serdes-ctrl
+ - const: syscon
+
+ "^dss-oldi-io-ctrl@[0-9a-f]+$":
+ type: object
+ $ref: /schemas/mfd/syscon.yaml#
+ properties:
+ compatible:
+ items:
+ - const: ti,am654-dss-oldi-io-ctrl
+ - const: syscon
+
+ "^clock-controller@[0-9a-f]+$":
+ type: object
+ $ref: /schemas/clock/ti,am654-ehrpwm-tbclk.yaml#
+ description:
+ Clock provider for TI EHRPWM nodes.
+
required:
- compatible
- reg
--
2.43.0
On Mon, Jun 24, 2024 at 08:20:49AM +0200, Jan Kiszka wrote: > From: Jan Kiszka <jan.kiszka@siemens.com> > > Expand bindings to cover both the MCU and the main usage of the AM654 > system controller. > > Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com> > --- > .../soc/ti/ti,am654-system-controller.yaml | 29 +++++++++++++++++++ > 1 file changed, 29 insertions(+) > > diff --git a/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml b/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml > index e79803e586ca..0eec807f38df 100644 > --- a/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml > +++ b/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml > @@ -34,6 +34,35 @@ patternProperties: > type: object > $ref: /schemas/phy/ti,phy-gmii-sel.yaml# > > + "^mux-controller$": > + type: object > + description: > + This is the SERDES lane control mux. Where is this object described? > + > + "^clock@[0-9a-f]+$": > + type: object > + $ref: /schemas/mfd/syscon.yaml# > + properties: > + compatible: > + items: > + - const: ti,am654-serdes-ctrl > + - const: syscon > + > + "^dss-oldi-io-ctrl@[0-9a-f]+$": > + type: object > + $ref: /schemas/mfd/syscon.yaml# > + properties: > + compatible: > + items: > + - const: ti,am654-dss-oldi-io-ctrl > + - const: syscon > + > + "^clock-controller@[0-9a-f]+$": > + type: object > + $ref: /schemas/clock/ti,am654-ehrpwm-tbclk.yaml# > + description: > + Clock provider for TI EHRPWM nodes. > + > required: > - compatible > - reg > -- > 2.43.0 >
On 24.06.24 18:24, Conor Dooley wrote: > On Mon, Jun 24, 2024 at 08:20:49AM +0200, Jan Kiszka wrote: >> From: Jan Kiszka <jan.kiszka@siemens.com> >> >> Expand bindings to cover both the MCU and the main usage of the AM654 >> system controller. >> >> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com> >> --- >> .../soc/ti/ti,am654-system-controller.yaml | 29 +++++++++++++++++++ >> 1 file changed, 29 insertions(+) >> >> diff --git a/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml b/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml >> index e79803e586ca..0eec807f38df 100644 >> --- a/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml >> +++ b/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml >> @@ -34,6 +34,35 @@ patternProperties: >> type: object >> $ref: /schemas/phy/ti,phy-gmii-sel.yaml# >> >> + "^mux-controller$": >> + type: object >> + description: >> + This is the SERDES lane control mux. > > Where is this object described? > Nowhere so far - I've only followed the pattern in mfd/ti,j721e-system-controller.yaml. Would adding "ref: /schemas/mux/reg-mux.yaml" be enough? Jan -- Siemens AG, Technology Linux Expert Center
On Mon, Jun 24, 2024 at 10:23:37PM +0200, Jan Kiszka wrote: > On 24.06.24 18:24, Conor Dooley wrote: > > On Mon, Jun 24, 2024 at 08:20:49AM +0200, Jan Kiszka wrote: > >> From: Jan Kiszka <jan.kiszka@siemens.com> > >> > >> Expand bindings to cover both the MCU and the main usage of the AM654 > >> system controller. > >> > >> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com> > >> --- > >> .../soc/ti/ti,am654-system-controller.yaml | 29 +++++++++++++++++++ > >> 1 file changed, 29 insertions(+) > >> > >> diff --git a/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml b/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml > >> index e79803e586ca..0eec807f38df 100644 > >> --- a/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml > >> +++ b/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml > >> @@ -34,6 +34,35 @@ patternProperties: > >> type: object > >> $ref: /schemas/phy/ti,phy-gmii-sel.yaml# > >> > >> + "^mux-controller$": > >> + type: object > >> + description: > >> + This is the SERDES lane control mux. > > > > Where is this object described? > > > > Nowhere so far - I've only followed the pattern in > mfd/ti,j721e-system-controller.yaml. Would adding "ref: > /schemas/mux/reg-mux.yaml" be enough? I think that would be okay, yea
© 2016 - 2026 Red Hat, Inc.