Browse Source

dt-bindings: fsi: Add optional chip-id to CFAMs

This represents a physical chip in the system and allows
a stable numbering scheme to be passed to udev for userspace
to recognize which chip is which.

Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Acked-by: Rob Herring <robh@kernel.org>
Benjamin Herrenschmidt 7 years ago
parent
commit
e13c542d52
1 changed files with 5 additions and 0 deletions
  1. 5 0
      Documentation/devicetree/bindings/fsi/fsi.txt

+ 5 - 0
Documentation/devicetree/bindings/fsi/fsi.txt

@@ -83,6 +83,10 @@ addresses and sizes in the slave address space:
     #address-cells = <1>;
     #address-cells = <1>;
     #size-cells = <1>;
     #size-cells = <1>;
 
 
+Optionally, a slave can provide a global unique chip ID which is used to
+identify the physical location of the chip in a system specific way
+
+    chip-id = <0>;
 
 
 FSI engines (devices)
 FSI engines (devices)
 ---------------------
 ---------------------
@@ -125,6 +129,7 @@ device tree if no extra platform information is required.
             reg = <0 0>;
             reg = <0 0>;
             #address-cells = <1>;
             #address-cells = <1>;
             #size-cells = <1>;
             #size-cells = <1>;
+	    chip-id = <0>;
 
 
             /* FSI engine at 0xc00, using a single page. In this example,
             /* FSI engine at 0xc00, using a single page. In this example,
              * it's an I2C master controller, so subnodes describe the
              * it's an I2C master controller, so subnodes describe the