[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210407185039.621248-2-varmam@google.com>
Date: Wed, 7 Apr 2021 11:50:38 -0700
From: Manish Varma <varmam@...gle.com>
To: Wolfram Sang <wsa@...nel.org>, Rob Herring <robh+dt@...nel.org>
Cc: linux-i2c@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, kernel-team@...roid.com,
Manish Varma <varmam@...gle.com>
Subject: [PATCH v1 1/2] dt-bindings: i2c: add "dev-name" property to assign
specific device name
I2C devices currently are named dynamically using
<adapter_id>-<device_address> convention, unless they are instantiated
through ACPI.
This means the device name may vary for the same device across different
systems, infact even on the same system if the I2C bus enumeration order
changes, i.e. because of device tree modifications.
By adding an optional "dev-name" property, it provides a mechanism to
set consistent and easy to recognize names for I2C devices.
Signed-off-by: Manish Varma <varmam@...gle.com>
---
Documentation/devicetree/bindings/i2c/i2c.txt | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/Documentation/devicetree/bindings/i2c/i2c.txt b/Documentation/devicetree/bindings/i2c/i2c.txt
index df41f72afc87..6fb03f464b81 100644
--- a/Documentation/devicetree/bindings/i2c/i2c.txt
+++ b/Documentation/devicetree/bindings/i2c/i2c.txt
@@ -130,6 +130,11 @@ wants to support one of the below features, it should adapt these bindings.
- wakeup-source
device can be used as a wakeup source.
+- dev-name
+ Name of the device.
+ Overrides the default device name which is in the form of
+ <busnr>-<addr>.
+
Binding may contain optional "interrupts" property, describing interrupts
used by the device. I2C core will assign "irq" interrupt (or the very first
interrupt if not using interrupt names) as primary interrupt for the slave.
--
2.31.1.295.g9ea45b61b8-goog
Powered by blists - more mailing lists