devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>,
	linux-i3c@lists.infradead.org, Rob Herring <robh+dt@kernel.org>,
	<devicetree@vger.kernel.org>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Conor Culhane <conor.culhane@silvaco.com>,
	Rajeev Huralikoppi <rajeev.huralikoppi@silvaco.com>,
	Nicolas Pitre <nico@fluxnic.net>,
	Miquel Raynal <miquel.raynal@bootlin.com>
Subject: [PATCH v5 2/6] dt-bindings: i3c: mipi-hci: Include the bus binding
Date: Thu, 21 Jan 2021 11:18:04 +0100	[thread overview]
Message-ID: <20210121101808.14654-3-miquel.raynal@bootlin.com> (raw)
In-Reply-To: <20210121101808.14654-1-miquel.raynal@bootlin.com>

Update a little bit the content to match the bus binding, including:
- the node title should have been named after the description done
  in the historical i3c.txt file, ie: i3c-master@<address>
- child nodes should be accepted even though the drivers do not currently
  support it
- #address-cells and #size-cells are also mandatory and have specific
  values

Cc: Nicolas Pitre <nico@fluxnic.net>
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
---
 Documentation/devicetree/bindings/i3c/mipi-i3c-hci.yaml | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/Documentation/devicetree/bindings/i3c/mipi-i3c-hci.yaml b/Documentation/devicetree/bindings/i3c/mipi-i3c-hci.yaml
index 07a7b10163a3..04da001fc6ec 100644
--- a/Documentation/devicetree/bindings/i3c/mipi-i3c-hci.yaml
+++ b/Documentation/devicetree/bindings/i3c/mipi-i3c-hci.yaml
@@ -9,6 +9,9 @@ title: MIPI I3C HCI Device Tree Bindings
 maintainers:
   - Nicolas Pitre <npitre@baylibre.com>
 
+allOf:
+  - $ref: /schemas/i3c/i3c.yaml#
+
 description: |
   MIPI I3C Host Controller Interface
 
@@ -36,12 +39,14 @@ required:
   - reg
   - interrupts
 
-additionalProperties: false
+unevaluatedProperties: false
 
 examples:
   - |
-    i3c@a0000000 {
+    i3c-master@a0000000 {
       compatible = "mipi-i3c-hci";
       reg = <0xa0000000 0x2000>;
       interrupts = <89>;
+      #address-cells = <3>;
+      #size-cells = <0>;
     };
-- 
2.20.1


  parent reply	other threads:[~2021-01-21 10:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-21 10:18 [PATCH v5 0/6] Silvaco I3C master driver Miquel Raynal
2021-01-21 10:18 ` [PATCH v5 1/6] dt-bindings: i3c: Convert the bus description to yaml Miquel Raynal
2021-02-05 21:31   ` Rob Herring
2021-01-21 10:18 ` Miquel Raynal [this message]
2021-02-05 21:31   ` [PATCH v5 2/6] dt-bindings: i3c: mipi-hci: Include the bus binding Rob Herring
2021-01-21 10:18 ` [PATCH v5 3/6] dt-bindings: Add vendor prefix for Silvaco Miquel Raynal
2021-01-21 10:18 ` [PATCH v5 4/6] dt-bindings: i3c: Describe Silvaco master binding Miquel Raynal
2021-01-21 10:18 ` [PATCH v5 5/6] i3c: master: svc: Add Silvaco I3C master driver Miquel Raynal
2021-01-21 10:18 ` [PATCH v5 6/6] MAINTAINERS: Add Silvaco I3C master Miquel Raynal
2021-02-05 23:44 ` [PATCH v5 0/6] Silvaco I3C master driver Alexandre Belloni

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=20210121101808.14654-3-miquel.raynal@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=conor.culhane@silvaco.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-i3c@lists.infradead.org \
    --cc=nico@fluxnic.net \
    --cc=rajeev.huralikoppi@silvaco.com \
    --cc=robh+dt@kernel.org \
    --cc=thomas.petazzoni@bootlin.com \
    /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).