@@ -9,8 +9,6 @@ Required Properties:
- compatible: should be one of the following,
"actions,s900-cmu"
"actions,s700-cmu"
-- reg: physical base address of the controller and length of memory mapped
- region.
- clocks: Reference to the parent clocks ("hosc", "losc")
- #clock-cells: should be 1.
@@ -21,6 +19,13 @@ All available clocks are defined as preprocessor macros in corresponding
dt-bindings/clock/actions,s900-cmu.h or actions,s700-cmu.h header and can be
used in device tree sources.
+The CMU registers are part of the system-controller block on Owl SoCs.
+
+Parent node should have the following properties :
+- compatible: "syscon", "simple-mfd"
+- reg: physical base address of the controller and length of memory mapped
+ region.
+
External clocks:
The hosc clock used as input for the plls is generated outside the SoC. It is
@@ -31,11 +36,15 @@ Actions Semi S900 CMU also requires one more clock:
Example: Clock Management Unit node:
- cmu: clock-controller@e0160000 {
- compatible = "actions,s900-cmu";
+ sysctrl: system-controller@e0160000 {
+ compatible = "syscon", "simple-mfd";
reg = <0x0 0xe0160000 0x0 0x1000>;
- clocks = <&hosc>, <&losc>;
- #clock-cells = <1>;
+
+ cmu: clock-controller {
+ compatible = "actions,s900-cmu";
+ clocks = <&hosc>, <&losc>;
+ #clock-cells = <1>;
+ };
};
Example: UART controller node that consumes clock generated by the clock
Since the clock and reset management units are sharing the same memory map, document the clock bindings to support System Controller. Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> --- .../bindings/clock/actions,owl-cmu.txt | 21 +++++++++++++------ 1 file changed, 15 insertions(+), 6 deletions(-) -- 2.17.1 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html