On Fri, Jul 17, 2026 at 05:59:17PM +0200, Miquel Raynal (Schneider Electric) wrote: > Hardware containers can just decouple external resources like clock > without any more control. Nexus nodes already exist for PWM and GPIOs, > add a binding to allow them for clocks as well. > > No examples are given, the file is litteraly a copy-paste from Hervé > Codina's work on PWM Nexus nodes, hence we just point to the examples > there which already illustrate very clearly the concept of the various > properties. > > Signed-off-by: Miquel Raynal (Schneider Electric) <[email protected]> > ---
Reviewed-by: Frank Li <[email protected]> > .../bindings/clock/clock-nexus-node.yaml | 30 > ++++++++++++++++++++++ > 1 file changed, 30 insertions(+) > > diff --git a/Documentation/devicetree/bindings/clock/clock-nexus-node.yaml > b/Documentation/devicetree/bindings/clock/clock-nexus-node.yaml > new file mode 100644 > index 000000000000..ff3283bd5fb1 > --- /dev/null > +++ b/Documentation/devicetree/bindings/clock/clock-nexus-node.yaml > @@ -0,0 +1,30 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/clock/clock-nexus-node.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Clock Nexus > + > +description: > > + A nexus node allows to remap a clock specifier list in a consumer node > + through a container or a connector node in a generic way. With this > + remapping, the consumer node needs to know only about the nexus > + node. Resources behind the nexus node are decoupled by the nexus node > + itself. > + > +maintainers: > + - Miquel Raynal <[email protected]> > + > +select: true > + > +properties: > + clock-map: > + $ref: /schemas/types.yaml#/definitions/uint32-matrix > + > +dependentRequired: > + clock-map: ['#clock-cells'] > + > +additionalProperties: true > + > +# See the original pwm-nexus-node.yaml description for examples > > -- > 2.54.0 >
