Quoting Nikita Shubin via B4 Relay (2023-07-20 04:29:02)
diff --git a/Documentation/devicetree/bindings/clock/cirrus,ep9301-clk.yaml b/Documentation/devicetree/bindings/clock/cirrus,ep9301-clk.yaml new file mode 100644 index 000000000000..111e016601fb --- /dev/null +++ b/Documentation/devicetree/bindings/clock/cirrus,ep9301-clk.yaml @@ -0,0 +1,46 @@ +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/clock/cirrus,ep9301-clk.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml#
+title: Cirrus Logic ep93xx SoC's clock controller
+maintainers:
- Nikita Shubin nikita.shubin@maquefel.me
- Alexander Sverdlin alexander.sverdlin@gmail.com
+properties:
- compatible:
- oneOf:
- const: cirrus,ep9301-clk- items:- enum:- cirrus,ep9302-clk- cirrus,ep9307-clk- cirrus,ep9312-clk- cirrus,ep9315-clk- const: cirrus,ep9301-clk- "#clock-cells":
- const: 1
- clocks:
- items:
- description: reference clock+required:
- compatible
- "#clock-cells"
- clocks
+additionalProperties: false
+examples:
- |
- clock-controller {
compatible = "cirrus,ep9301-clk";
Is there a reg property? The driver grabs some syscon and then iomaps it, so presumably there is a register range. Is it part of some other hardware block? If so, can you make that device register sub-devices with the auxiliary bus instead of using a syscon?