devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eddie James <eajames@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: gregkh@linuxfoundation.org, devicetree@vger.kernel.org,
	robh+dt@kernel.org, mark.rutland@arm.com,
	bradleyb@fuzziesquirrel.com, jk@ozlabs.org,
	cbostic@linux.vnet.ibm.com, joel@jms.id.au, andrew@aj.id.au,
	eajames@linux.vnet.ibm.com,
	"Edward A. James" <eajames@us.ibm.com>
Subject: [PATCH v3 4/6] dt-bindings: fsi: Add OCC documentation
Date: Fri, 22 Sep 2017 16:06:00 -0500	[thread overview]
Message-ID: <1506114362-492-5-git-send-email-eajames@linux.vnet.ibm.com> (raw)
In-Reply-To: <1506114362-492-1-git-send-email-eajames@linux.vnet.ibm.com>

From: "Edward A. James" <eajames@us.ibm.com>

Document the bindings for the P9 OCC device. OCC devices are accessed
through the SBEFIFO.

Signed-off-by: Edward A. James <eajames@us.ibm.com>
---
 Documentation/devicetree/bindings/fsi/ibm,p9-occ.txt | 15 +++++++++++++++
 1 file changed, 15 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/fsi/ibm,p9-occ.txt

diff --git a/Documentation/devicetree/bindings/fsi/ibm,p9-occ.txt b/Documentation/devicetree/bindings/fsi/ibm,p9-occ.txt
new file mode 100644
index 0000000..bcaefc9
--- /dev/null
+++ b/Documentation/devicetree/bindings/fsi/ibm,p9-occ.txt
@@ -0,0 +1,15 @@
+Device-tree bindings for P9 On-Chip Controller
+----------------------------------------------
+
+Required properties:
+ - compatible = "ibm,p9-occ";
+
+Optional properties:
+ - reg = <processor index>;	: Index for the processor this OCC is on.
+
+Examples:
+
+    occ@1 {
+        compatible = "ibm,p9-occ";
+        reg = <1>;
+    };
-- 
1.8.3.1

  parent reply	other threads:[~2017-09-22 21:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-22 21:05 [PATCH v3 0/6] drivers: fsi: Add SBEFIFO and OCC drivers Eddie James
2017-09-22 21:05 ` [PATCH v3 1/6] dt-bindings: fsi: Add SBEFIFO documentation Eddie James
     [not found]   ` <1506114362-492-2-git-send-email-eajames-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2017-10-04 20:58     ` Rob Herring
2017-09-22 21:05 ` [PATCH v3 2/6] drivers: fsi: Add SBEFIFO FSI client device driver Eddie James
     [not found]   ` <1506114362-492-3-git-send-email-eajames-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2017-09-29 20:37     ` Andrew Jeffery
2017-09-22 21:05 ` [PATCH v3 3/6] drivers: fsi: sbefifo: Add in-kernel API Eddie James
2017-09-22 21:06 ` Eddie James [this message]
     [not found]   ` <1506114362-492-5-git-send-email-eajames-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2017-10-04 20:59     ` [PATCH v3 4/6] dt-bindings: fsi: Add OCC documentation Rob Herring
2017-09-22 21:06 ` [PATCH v3 5/6] drivers: fsi: Add On-Chip Controller (OCC) driver Eddie James
2017-09-22 21:06 ` [PATCH v3 6/6] drivers: fsi: occ: Add in-kernel API Eddie James

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=1506114362-492-5-git-send-email-eajames@linux.vnet.ibm.com \
    --to=eajames@linux.vnet.ibm.com \
    --cc=andrew@aj.id.au \
    --cc=bradleyb@fuzziesquirrel.com \
    --cc=cbostic@linux.vnet.ibm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=eajames@us.ibm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jk@ozlabs.org \
    --cc=joel@jms.id.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.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).