From: Eddie James <eajames-tEXmvtCZX7AybS5Ee8rs3A@public.gmane.org>
To: linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
joel-U3u1mxZcP9KHXe+LvDLADg@public.gmane.org,
andrew-zrmu5oMJ5Fs@public.gmane.org,
andy.shevchenko-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Eddie James <eajames-tEXmvtCZX7AybS5Ee8rs3A@public.gmane.org>
Subject: [PATCH v3 1/2] dt-bindings: fsi: Add FSI2SPI bindings
Date: Fri, 6 Mar 2020 13:41:17 -0600 [thread overview]
Message-ID: <20200306194118.18581-2-eajames@linux.ibm.com> (raw)
In-Reply-To: <20200306194118.18581-1-eajames-tEXmvtCZX7AybS5Ee8rs3A@public.gmane.org>
Add documentation for the FSI2SPI CFAM engine, which provides access to
a number of SPI controllers.
Signed-off-by: Eddie James <eajames-tEXmvtCZX7AybS5Ee8rs3A@public.gmane.org>
---
.../devicetree/bindings/fsi/ibm,fsi2spi.yaml | 36 +++++++++++++++++++
1 file changed, 36 insertions(+)
create mode 100644 Documentation/devicetree/bindings/fsi/ibm,fsi2spi.yaml
diff --git a/Documentation/devicetree/bindings/fsi/ibm,fsi2spi.yaml b/Documentation/devicetree/bindings/fsi/ibm,fsi2spi.yaml
new file mode 100644
index 000000000000..893d81e54caa
--- /dev/null
+++ b/Documentation/devicetree/bindings/fsi/ibm,fsi2spi.yaml
@@ -0,0 +1,36 @@
+# SPDX-License-Identifier: (GPL-2.0-or-later)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/fsi/ibm,fsi2spi.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: IBM FSI-attached SPI controllers
+
+maintainers:
+ - Eddie James <eajames-tEXmvtCZX7AybS5Ee8rs3A@public.gmane.org>
+
+description: |
+ This binding describes an FSI CFAM engine called the FSI2SPI. Therefore this
+ node will always be a child of an FSI CFAM node; see fsi.txt for details on
+ FSI slave and CFAM nodes. This FSI2SPI engine provides access to a number of
+ SPI controllers.
+
+properties:
+ compatible:
+ enum:
+ - ibm,fsi2spi
+
+ reg:
+ items:
+ - description: FSI slave address
+
+required:
+ - compatible
+ - reg
+
+examples:
+ - |
+ fsi2spi@1c00 {
+ compatible = "ibm,fsi2spi";
+ reg = <0x1c00 0x400>;
+ };
--
2.24.0
next prev parent reply other threads:[~2020-03-06 19:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 19:41 [PATCH v3 0/2] spi: Add FSI-attached SPI controller driver Eddie James
[not found] ` <20200306194118.18581-1-eajames-tEXmvtCZX7AybS5Ee8rs3A@public.gmane.org>
2020-03-06 19:41 ` Eddie James [this message]
[not found] ` <20200306194118.18581-2-eajames-tEXmvtCZX7AybS5Ee8rs3A@public.gmane.org>
2020-03-10 14:31 ` Applied "dt-bindings: fsi: Add FSI2SPI bindings" to the spi tree Mark Brown
2020-03-06 19:41 ` [PATCH v3 2/2] spi: Add FSI-attached SPI controller driver Eddie James
2020-03-10 14:31 ` Applied "spi: Add FSI-attached SPI controller driver" to the spi tree Mark Brown
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=20200306194118.18581-2-eajames@linux.ibm.com \
--to=eajames-texmvtczx7aybs5ee8rs3a@public.gmane.org \
--cc=andrew-zrmu5oMJ5Fs@public.gmane.org \
--cc=andy.shevchenko-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=joel-U3u1mxZcP9KHXe+LvDLADg@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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).