From: Vitor Soares <Vitor.Soares@synopsys.com>
To: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-i3c@lists.infradead.org
Cc: bbrezillon@kernel.org, robh+dt@kernel.org, mark.rutland@arm.com,
pgaj@cadence.com, Joao.Pinto@synopsys.com,
Vitor Soares <Vitor.Soares@synopsys.com>
Subject: [PATCH v2 3/5] dt-bindings: i3c: Make 'assigned-address' valid if static address == 0
Date: Tue, 3 Sep 2019 12:35:52 +0200 [thread overview]
Message-ID: <c0505ef73add4512ce1ee2a71b1c8bc8f771151b.1567437955.git.vitor.soares@synopsys.com> (raw)
In-Reply-To: <cover.1567437955.git.vitor.soares@synopsys.com>
In-Reply-To: <cover.1567437955.git.vitor.soares@synopsys.com>
The I3C devices without a static address can require a specific dynamic
address for priority reasons.
Let's update the binding document to make the 'assigned-address' property
valid if static address == 0 and add an example with this use case.
Signed-off-by: Vitor Soares <vitor.soares@synopsys.com>
---
Documentation/devicetree/bindings/i3c/i3c.txt | 13 ++++++++++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git a/Documentation/devicetree/bindings/i3c/i3c.txt b/Documentation/devicetree/bindings/i3c/i3c.txt
index ab729a0..c851e75 100644
--- a/Documentation/devicetree/bindings/i3c/i3c.txt
+++ b/Documentation/devicetree/bindings/i3c/i3c.txt
@@ -98,9 +98,7 @@ Required properties
Optional properties
-------------------
-- assigned-address: dynamic address to be assigned to this device. This
- property is only valid if the I3C device has a static
- address (first cell of the reg property != 0).
+- assigned-address: dynamic address to be assigned to this device.
Example:
@@ -129,6 +127,15 @@ Example:
/*
* I3C device without a static I2C address but requiring
+ * specific dynamic address.
+ */
+ sensor@0,39200154004 {
+ reg = <0x0 0x6072 0x303904d2>;
+ assigned-address = <0xb>;
+ };
+
+ /*
+ * I3C device without a static I2C address but requiring
* resources described in the DT.
*/
sensor@0,39200154004 {
--
2.7.4
next prev parent reply other threads:[~2019-09-03 10:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 10:35 [PATCH v2 0/5] i3c: remove device if failed on pre_assign_dyn_addr() Vitor Soares
2019-09-03 10:35 ` [PATCH v2 1/5] i3c: master: detach and free device if pre_assign_dyn_addr() fails Vitor Soares
2019-09-03 10:52 ` Boris Brezillon
2019-09-03 11:10 ` Vitor Soares
2019-09-03 11:13 ` Przemyslaw Gaj
2019-09-03 11:57 ` Vitor Soares
2019-09-04 4:47 ` Przemyslaw Gaj
2019-09-04 9:06 ` Vitor Soares
2019-09-03 10:35 ` [PATCH v2 2/5] i3c: master: make sure ->boardinfo is initialized in add_i3c_dev_locked() Vitor Soares
2019-09-03 10:35 ` Vitor Soares [this message]
2019-09-03 17:40 ` [PATCH v2 3/5] dt-bindings: i3c: Make 'assigned-address' valid if static address == 0 Rob Herring
2019-09-03 10:35 ` [PATCH v2 4/5] dt-bindings: i3c: add a note for no guarantee of 'assigned-address' use Vitor Soares
2019-09-03 17:41 ` Rob Herring
2019-09-03 10:35 ` [PATCH v2 5/5] i3c: master: dw: reattach device on first available location of address table Vitor Soares
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c0505ef73add4512ce1ee2a71b1c8bc8f771151b.1567437955.git.vitor.soares@synopsys.com \
--to=vitor.soares@synopsys.com \
--cc=Joao.Pinto@synopsys.com \
--cc=bbrezillon@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pgaj@cadence.com \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).