Add an example showing how to use the addr-gpios property to deal with a
system with limited IO space.

Cc: devicet...@vger.kernel.org
Signed-off-by: Chris Packham <chris.pack...@alliedtelesis.co.nz>
---
 .../devicetree/bindings/mtd/mtd-physmap.txt      | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/Documentation/devicetree/bindings/mtd/mtd-physmap.txt 
b/Documentation/devicetree/bindings/mtd/mtd-physmap.txt
index 7df0dcaccb7d..c69f4f065d23 100644
--- a/Documentation/devicetree/bindings/mtd/mtd-physmap.txt
+++ b/Documentation/devicetree/bindings/mtd/mtd-physmap.txt
@@ -96,3 +96,19 @@ An example using SRAM:
                bank-width = <2>;
        };
 
+An example using gpio-addrs
+
+       flash@20000000 {
+               #address-cells = <1>;
+               #size-cells = <1>;
+               compatible = "cfi-flash", "jedec-flash";
+               reg = <0x20000000 0x02000000>;
+               ranges = <0 0x00000000 0x02000000
+                         1 0x02000000 0x02000000>;
+               bank-width = <2>;
+               addr-gpios = <&gpio1 2 GPIO_ACTIVE_HIGH>;
+               partition@0 {
+                       label = "test-part1";
+                       reg = <0 0x04000000>;
+               };
+       };
-- 
2.21.0

Reply via email to