From: Nicolas Pitre <nico@fluxnic.net>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, Robert Gough <robert.gough@intel.com>,
Laura Nixon <laura.nixon@team.mipi.org>,
Boris Brezillon <boris.brezillon@collabora.com>,
Sakari Ailus <sakari.ailus@iki.fi>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Matthew Schnoor <matthew.schnoor@intel.com>,
linux-i3c@lists.infradead.org
Subject: Re: [PATCH v3 1/2] dt-bindings: i3c: MIPI I3C Host Controller Interface
Date: Wed, 4 Nov 2020 14:28:22 -0500 (EST) [thread overview]
Message-ID: <nycvar.YSQ.7.78.906.2011041420420.2184@knanqh.ubzr> (raw)
In-Reply-To: <20201104183459.GA3917393@bogus>
On Wed, 4 Nov 2020, Rob Herring wrote:
> On Mon, Nov 02, 2020 at 05:22:19PM -0500, Nicolas Pitre wrote:
> > From: Nicolas Pitre <npitre@baylibre.com>
> >
> > The MIPI I3C HCI (Host Controller Interface) specification defines
> > a common software driver interface to support compliant MIPI I3C
> > host controller hardware implementations from multiple vendors.
> >
> > All that is needed is an I/O area and an interrupt signal;. The hardware
> > is self-advertising wrt its implementor and implemented capabilities so
> > there is currently no details that the driver can't figure out on its own.
> >
> > Signed-off-by: Nicolas Pitre <npitre@baylibre.com>
> > ---
> > .../devicetree/bindings/i3c/mipi-i3c-hci.yaml | 45 +++++++++++++++++++
> > 1 file changed, 45 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/i3c/mipi-i3c-hci.yaml
>
> With additionalProperties added,
>
> Reviewed-by: Rob Herring <robh@kernel.org>
Thanks. Fixed patch below.
----- >8
From: Nicolas Pitre <npitre@baylibre.com>
Subject: [PATCH] dt-bindings: i3c: MIPI I3C Host Controller Interface
The MIPI I3C HCI (Host Controller Interface) specification defines
a common software driver interface to support compliant MIPI I3C
host controller hardware implementations from multiple vendors.
All that is needed is an I/O area and an interrupt signal;. The hardware
is self-advertising wrt its implementor and implemented capabilities so
there is currently no details that the driver can't figure out on its own.
Signed-off-by: Nicolas Pitre <npitre@baylibre.com>
Reviewed-by: Rob Herring <robh@kernel.org>
diff --git a/Documentation/devicetree/bindings/i3c/mipi-i3c-hci.yaml b/Documentation/devicetree/bindings/i3c/mipi-i3c-hci.yaml
new file mode 100644
index 0000000000..07a7b10163
--- /dev/null
+++ b/Documentation/devicetree/bindings/i3c/mipi-i3c-hci.yaml
@@ -0,0 +1,47 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: "http://devicetree.org/schemas/i3c/mipi-i3c-hci.yaml#"
+$schema: "http://devicetree.org/meta-schemas/core.yaml#"
+
+title: MIPI I3C HCI Device Tree Bindings
+
+maintainers:
+ - Nicolas Pitre <npitre@baylibre.com>
+
+description: |
+ MIPI I3C Host Controller Interface
+
+ The MIPI I3C HCI (Host Controller Interface) specification defines
+ a common software driver interface to support compliant MIPI I3C
+ host controller hardware implementations from multiple vendors.
+
+ The hardware is self-advertising for differences in implementation
+ capabilities, including the spec version it is based on, so there
+ isn't much to describe here (yet).
+
+ For details, please see:
+ https://www.mipi.org/specifications/i3c-hci
+
+properties:
+ compatible:
+ const: mipi-i3c-hci
+ reg:
+ maxItems: 1
+ interrupts:
+ maxItems: 1
+
+required:
+ - compatible
+ - reg
+ - interrupts
+
+additionalProperties: false
+
+examples:
+ - |
+ i3c@a0000000 {
+ compatible = "mipi-i3c-hci";
+ reg = <0xa0000000 0x2000>;
+ interrupts = <89>;
+ };
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
next prev parent reply other threads:[~2020-11-04 19:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 22:22 [PATCH v3 0/2] MIPI I3c HCI (Host Controller Interface) driver Nicolas Pitre
2020-11-02 22:22 ` [PATCH v3 1/2] dt-bindings: i3c: MIPI I3C Host Controller Interface Nicolas Pitre
2020-11-04 18:33 ` Rob Herring
2020-11-04 18:34 ` Rob Herring
2020-11-04 19:28 ` Nicolas Pitre [this message]
2020-11-02 22:22 ` [PATCH v3 2/2] i3c/master: introduce the mipi-i3c-hci driver Nicolas Pitre
2020-11-10 11:09 ` kernel test robot
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=nycvar.YSQ.7.78.906.2011041420420.2184@knanqh.ubzr \
--to=nico@fluxnic.net \
--cc=boris.brezillon@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=laura.nixon@team.mipi.org \
--cc=linux-i3c@lists.infradead.org \
--cc=matthew.schnoor@intel.com \
--cc=miquel.raynal@bootlin.com \
--cc=robert.gough@intel.com \
--cc=robh@kernel.org \
--cc=sakari.ailus@iki.fi \
/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).