On Wed, Oct 06, 2021 at 08:09:14PM +0900, Kunihiko Hayashi wrote:Following the previous three examples in the document, it describes the
Update binding document for clocks implemented in SoC-glue.++++++++++++++++
Signed-off-by: Kunihiko Hayashi <hayashi.kunihiko@xxxxxxxxxxxxx>
---
.../bindings/clock/socionext,uniphier-clock.yaml | 16
1 file changed, 16 insertions(+)a/Documentation/devicetree/bindings/clock/socionext,uniphier-clock.yaml
diff --git
b/Documentation/devicetree/bindings/clock/socionext,uniphier-clock.yaml
index ee8d16a8019e..05a9d1f89756 100644a/Documentation/devicetree/bindings/clock/socionext,uniphier-clock.yaml
---
+++b/Documentation/devicetree/bindings/clock/socionext,uniphier-clock.yaml
@@ -46,6 +46,9 @@ properties:"syscon";
- socionext,uniphier-ld20-peri-clock
- socionext,uniphier-pxs3-peri-clock
- socionext,uniphier-nx1-peri-clock
+ - description: SoC-glue clock
+ enum:
+ - socionext,uniphier-pro4-sg-clock
"#clock-cells":
const: 1
@@ -95,3 +98,16 @@ examples:
// other nodes ...
};
+
+ - |
+ soc-glue@5f800000 {
+ compatible = "socionext,uniphier-sysctrl", "simple-mfd",
+ reg = <0x5f800000 0x2000>;
+
+ clock {
+ compatible = "socionext,uniphier-pro4-sg-clock";
+ #clock-cells = <1>;
+ };
+
+ // other nodes ...
+ };
What's the value of this 2nd example? It's just a different compatible
string.