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: default avatarBenjamin Herrenschmidt <benh@kernel.crashing.org>
Acked-by: default avatarRob Herring <robh@kernel.org>
parent 4fcdc2d1
...@@ -83,6 +83,10 @@ addresses and sizes in the slave address space: ...@@ -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. ...@@ -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
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment