LKML Archive on lore.kernel.org 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, cbostic@linux.vnet.ibm.com, joel@jms.id.au, eajames@linux.vnet.ibm.com, "Edward A. James" <eajames@us.ibm.com> Subject: [PATCH v5 5/8] dt-bindings: fsi: Add OCC documentation Date: Mon, 20 Nov 2017 13:46:54 -0600 [thread overview] Message-ID: <1511207217-14075-6-git-send-email-eajames@linux.vnet.ibm.com> (raw) In-Reply-To: <1511207217-14075-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 | 18 ++++++++++++++++++ 1 file changed, 18 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..79094f5 --- /dev/null +++ b/Documentation/devicetree/bindings/fsi/ibm,p9-occ.txt @@ -0,0 +1,18 @@ +Device-tree bindings for P9 On-Chip Controller +---------------------------------------------- + +The POWER9 On-Chip Controller is accessed through the SBEFIFO. All OCC nodes +must be child nodes of SBEFIFO devices (see ibm,p9-sbefifo.txt). + +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
next prev parent reply other threads:[~2017-11-20 19:47 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-11-20 19:46 [PATCH v5 0/8] drivers/fsi: Add SBEFIFO and OCC client drivers Eddie James 2017-11-20 19:46 ` [PATCH v5 1/8] dt-bindings: fsi: Add SBEFIFO documentation Eddie James 2017-11-20 21:35 ` Rob Herring 2017-11-20 19:46 ` [PATCH v5 2/8] drivers/fsi: Add SBEFIFO FSI client device driver Eddie James 2017-11-20 19:46 ` [PATCH v5 3/8] drivers/fsi: sbefifo: Add miscdevice Eddie James 2017-11-20 19:46 ` [PATCH v5 4/8] drivers/fsi: sbefifo: Add in-kernel API Eddie James 2017-11-23 9:50 ` kbuild test robot 2017-11-20 19:46 ` Eddie James [this message] 2017-11-20 21:39 ` [PATCH v5 5/8] dt-bindings: fsi: Add OCC documentation Rob Herring 2017-11-20 22:03 ` Eddie James 2017-11-20 23:41 ` Rob Herring 2017-11-20 19:46 ` [PATCH v5 6/8] drivers/fsi: Add On-Chip Controller (OCC) driver Eddie James 2017-11-20 19:46 ` [PATCH v5 7/8] drivers/fsi: occ: Add miscdevice Eddie James 2017-11-20 19:46 ` [PATCH v5 8/8] drivers/fsi: occ: Add in-kernel API Eddie James 2017-11-23 16:33 ` kbuild test robot 2017-11-23 16:56 ` kbuild 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=1511207217-14075-6-git-send-email-eajames@linux.vnet.ibm.com \ --to=eajames@linux.vnet.ibm.com \ --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=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: linkBe 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).