The Calxeda sata_highbank driver has been adding its descriptions to the
ahci driver. Separate them properly. This patch only affects
documentation and has no functional component.

Signed-off-by: Mark Langsdorf <[email protected]>
Acked-by: Rob Herring <[email protected]>
---
Changes from v3
        Added all optional properties to the example.
        Expanded the description.
        Renumbered the patch series since the first two got accepted.
Changes from v2
        Fixed some indenting.
Changes from v1
        None.

 Documentation/devicetree/bindings/ata/sata_highbank.txt | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/Documentation/devicetree/bindings/ata/sata_highbank.txt 
b/Documentation/devicetree/bindings/ata/sata_highbank.txt
index 1ac6d3d..e7a6f28 100644
--- a/Documentation/devicetree/bindings/ata/sata_highbank.txt
+++ b/Documentation/devicetree/bindings/ata/sata_highbank.txt
@@ -12,7 +12,7 @@ Required properties:
 
 Optional properties:
 - dma-coherent      : Present if dma operations are coherent
-- calxeda,port-phys: phandle-combophy and lane assignment, which maps each
+- calxeda,port-phys : phandle-combophy and lane assignment, which maps each
                        SATA port to a combophy and a lane within that
                        combophy
 - calxeda,sgpio-gpio: phandle-gpio bank, bit offset, and default on or off,
@@ -26,7 +26,9 @@ Example:
                compatible = "calxeda,hb-ahci";
                reg = <0xffe08000 0x1000>;
                interrupts = <115>;
+               dma-coherent;
                calxeda,port-phys = <&combophy5 0 &combophy0 0 &combophy0 1
                                        &combophy0 2 &combophy0 3>;
-
+               calxeda,sgpio-gpio =<&gpioh 5 1 &gpioh 6 1 &gpioh 7 1>;
+               calxeda,led-order = <4 0 1 2 3>;
         };
-- 
1.8.1.2

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to