From: Mikko Perttunen <mperttu...@nvidia.com>
Sometimes, hardware blocks want to issue requests to devices
connected to I2C buses by itself. In such case, the bus the
target device resides on must be configured into a register.
For this purpose, each I2C controller has a defined ID known
by the hardware. Add a property for these IDs to the device tree
bindings, so that drivers can know what ID to write to a hardware
register when configuring a block that sends I2C messages autonomously.
Signed-off-by: Mikko Perttunen <mperttu...@nvidia.com>
Reviewed-by: Wei Ni <w...@nvidia.com>
Tested-by: Wei Ni <w...@nvidia.com>
---
Documentation/devicetree/bindings/i2c/nvidia,tegra20-i2c.txt | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/Documentation/devicetree/bindings/i2c/nvidia,tegra20-i2c.txt
b/Documentation/devicetree/bindings/i2c/nvidia,tegra20-i2c.txt
index 87507e9..e9e5994 100644
--- a/Documentation/devicetree/bindings/i2c/nvidia,tegra20-i2c.txt
+++ b/Documentation/devicetree/bindings/i2c/nvidia,tegra20-i2c.txt
@@ -57,6 +57,10 @@ Required properties:
- rx
- tx
+Optional properties:
+- nvidia,controller-id: ID of controller when referred to in
+ hardware registers.
+
Example:
i2c@7000c000 {
@@ -71,5 +75,6 @@ Example:
reset-names = "i2c";
dmas = <&apbdma 16>, <&apbdma 16>;
dma-names = "rx", "tx";
+ nvidia,controller-id = <0>;
status = "disabled";
};
--
2.1.0
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
