This patch updates the binding documentation for optional
clocks node and related information for buffered 32KHz clock.
Signed-off-by: Vaibhav Hiremath <vaibhav.hiremath@xxxxxxxxxx>
---
Documentation/devicetree/bindings/mfd/88pm800.txt | 28 +++++++++++++++++++++++
1 file changed, 28 insertions(+)
diff --git a/Documentation/devicetree/bindings/mfd/88pm800.txt b/Documentation/devicetree/bindings/mfd/88pm800.txt
index dec842f..60cab78 100644
--- a/Documentation/devicetree/bindings/mfd/88pm800.txt
+++ b/Documentation/devicetree/bindings/mfd/88pm800.txt
@@ -9,6 +9,27 @@ Required parent device properties:
- #interrupt-cells : should be 1.
The cell is the 88pm80x local IRQ number
+Optional nodes:
+- clocks: 88pm800 family of devices provide multiple buffered 32.768
+ KHz outputs, so to register these as clocks with common clock framework
+ instantiate a sub-node named "clocks". It uses the common clock binding
+ documented in :
+ [Documentation/devicetree/bindings/clock/clock-bindings.txt]
+
+ - #clock-cells: should be 1.
+
+ - The following is the list of clocks generated by the controller. Each clock
+ is assigned an identifier and client nodes use this identifier to specify
+ the clock which they consume.
+ Clock ID Devices
+ ----------------------------------------------------------
+ pm800_clk32k_1 0 88PM800 and 88PM860
+ pm800_clk32k_2 1 88PM800 and 88PM860
+ pm800_clk32k_3 2 88PM800
+
+ - compatible: Should be : "marvell,88pm800-clk"
+
+
88pm80x family of devices consists of varied group of sub-devices:
Device Supply Names Description
@@ -16,6 +37,7 @@ Device Supply Names Description
88pm80x-onkey : : On key
88pm80x-rtc : : RTC
88pm80x-regulator : : Regulators
+88pm80x-clk : : 32KHz Clk provider
Example:
@@ -27,6 +49,12 @@ Example:
interrupt-controller;
#interrupt-cells = <1>;
+ pm800clk: clocks {
+ compatible = "marvell,88pm800-clk";
+ #clock-cells = <1>;
+ clock-output-names = "xx", "yy", "zz";
+ };
+
regulators {
compatible = "marvell,88pm80x-regulator";
--
1.9.1
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
