[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <f8a0cbc92605dbf5f41a28edd7691c3e90087554.1567608245.git.vitor.soares@synopsys.com>
Date: Thu, 5 Sep 2019 12:00:37 +0200
From: Vitor Soares <Vitor.Soares@...opsys.com>
To: linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
linux-i3c@...ts.infradead.org
Cc: bbrezillon@...nel.org, robh+dt@...nel.org, mark.rutland@....com,
pgaj@...ence.com, Joao.Pinto@...opsys.com,
Vitor Soares <Vitor.Soares@...opsys.com>
Subject: [PATCH v3 4/5] dt-bindings: i3c: add a note for no guarantee of 'assigned-address' use
By default, the framework will try to assign the 'assigned-address' to the
device but if the address is already in use the device dynamic address
will be different.
Signed-off-by: Vitor Soares <vitor.soares@...opsys.com>
Reviewed-by: Rob Herring <robh@...nel.org>
---
Change in v3:
- Add Rob rb-tag
Documentation/devicetree/bindings/i3c/i3c.txt | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/i3c/i3c.txt b/Documentation/devicetree/bindings/i3c/i3c.txt
index c851e75..e777f09 100644
--- a/Documentation/devicetree/bindings/i3c/i3c.txt
+++ b/Documentation/devicetree/bindings/i3c/i3c.txt
@@ -98,7 +98,9 @@ Required properties
Optional properties
-------------------
-- assigned-address: dynamic address to be assigned to this device.
+- assigned-address: dynamic address to be assigned to this device. The framework
+ will try to assign this dynamic address but if something
+ fails the device dynamic address will be different.
Example:
--
2.7.4
Powered by blists - more mailing lists