The Berlin SATA PHY drives the PHY related to the SATA interface and
allows to power up/down each PHY independently. Add the corresponding
documentation.
Signed-off-by: Antoine Ténart <antoine.tenart@xxxxxxxxxxxxxxxxxx>
---
.../devicetree/bindings/phy/berlin-sata-phy.txt | 34 ++++++++++++++++++++++
1 file changed, 34 insertions(+)
create mode 100644 Documentation/devicetree/bindings/phy/berlin-sata-phy.txt
diff --git a/Documentation/devicetree/bindings/phy/berlin-sata-phy.txt b/Documentation/devicetree/bindings/phy/berlin-sata-phy.txt
new file mode 100644
index 000000000000..b1e11a25775a
--- /dev/null
+++ b/Documentation/devicetree/bindings/phy/berlin-sata-phy.txt
@@ -0,0 +1,34 @@
+Berlin SATA PHY
+---------------
+
+Required properties:
+- compatible: "marvell,berlin-sata-phy"
+- #address-cells: number of cells to encode an address, must be 1
+- #size-cells: number of cells representing the size of an address, must be 0
+- reg: address and length of the register
+
+The SATA PHY node is a provider and should contain sub-nodes representing the
+PHYs it handles, one per PHY.
+
+Required sub-node properties:
+- reg: the PHY described. 0 or 1.
+- #phy-cells: from the generic PHY bindings, must be 0
+
+Example:
+ sata_phy: phy@f7e900a0 {
+ compatible = "marvell,berlin-sata-phy";
+ reg = <0xf7e900a0 0x10>;
+ #address-cells = <1>;
+ #size-cells = <0>;
+ status = "okay";
+
+ sata_phy0: phy@0 {
+ reg = <0>;
+ #phy-cells = <0>;
+ };
+
+ sata_phy1: phy@1 {
+ reg = <1>;
+ #phy-cells = <0>;
+ };
+ };
--
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
