Quoting Inochi Amaoto (2025-02-26 15:23:18) > diff --git a/Documentation/devicetree/bindings/clock/sophgo,sg2044-clk.yaml b/Documentation/devicetree/bindings/clock/sophgo,sg2044-clk.yaml > new file mode 100644 > index 000000000000..d55c5d32e206 > --- /dev/null > +++ b/Documentation/devicetree/bindings/clock/sophgo,sg2044-clk.yaml > @@ -0,0 +1,40 @@ > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/clock/sophgo,sg2044-clk.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Sophgo SG2044 Clock Controller > + > +maintainers: > + - Inochi Amaoto <inochiama@xxxxxxxxx> No description? > + > +properties: > + compatible: > + const: sophgo,sg2044-clk > + > + reg: > + maxItems: 1 > + > + clocks: > + maxItems: 1 > + > + '#clock-cells': > + const: 1 > + > +required: > + - compatible > + - reg > + - clocks > + - '#clock-cells' > + > +additionalProperties: false > + > +examples: > + - | > + clock-controller@50002000 { > + compatible = "sophgo,sg2044-clk"; > + reg = <0x50002000 0x1000>; > + #clock-cells = <1>; > + clocks = <&osc>; I think you want the syscon phandle here as another property. Doing that will cause the DT parsing logic to wait for the syscon to be probed before trying to probe this driver. It's also useful so we can see if the clock controller is overlapping withe whatever the syscon node is, or if that syscon node should just have the #clock-cells property as part of the node instead.
