From: Eddie James <eajames@linux.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
jdelvare@suse.com, linux-doc@vger.kernel.org,
gregkh@linuxfoundation.org, robh+dt@kernel.org,
mark.rutland@arm.com, linux@roeck-us.net, rdunlap@infradead.org,
benh@kernel.crashing.org,
Eddie James <eajames@linux.vnet.ibm.com>,
Eddie James <eajames@linux.ibm.com>
Subject: [PATCH v6 01/10] dt-bindings: fsi: Add P9 OCC device documentation
Date: Thu, 8 Nov 2018 15:05:20 -0600 [thread overview]
Message-ID: <1541711129-26631-2-git-send-email-eajames@linux.ibm.com> (raw)
In-Reply-To: <1541711129-26631-1-git-send-email-eajames@linux.ibm.com>
From: Eddie James <eajames@linux.vnet.ibm.com>
Document the bindings for the FSI-attached POWER9 On-Chip Controller.
Signed-off-by: Eddie James <eajames@linux.ibm.com>
---
Documentation/devicetree/bindings/fsi/ibm,p9-occ.txt | 16 ++++++++++++++++
1 file changed, 16 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..99ca986
--- /dev/null
+++ b/Documentation/devicetree/bindings/fsi/ibm,p9-occ.txt
@@ -0,0 +1,16 @@
+Device-tree bindings for FSI-attached POWER9 On-Chip Controller (OCC)
+---------------------------------------------------------------------
+
+This is the binding for the P9 On-Chip Controller accessed over FSI from a
+service processor. See fsi.txt for details on bindings for FSI slave and CFAM
+nodes. The OCC is not an FSI slave device itself, rather it is accessed
+through the SBE fifo.
+
+Required properties:
+ - compatible = "ibm,p9-occ"
+
+Examples:
+
+ occ {
+ compatible = "ibm,p9-occ";
+ };
--
1.8.3.1
next prev parent reply other threads:[~2018-11-08 21:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 21:05 [PATCH v6 00/10] hwmon and fsi: Add On-Chip Controller Driver Eddie James
2018-11-08 21:05 ` Eddie James [this message]
2018-11-08 21:05 ` [PATCH v6 02/10] fsi: Add On-Chip Controller (OCC) driver Eddie James
2018-11-08 21:05 ` [PATCH v6 03/10] Documentation: hwmon: Add OCC documentation Eddie James
2018-11-08 21:05 ` [PATCH v6 04/10] dt-bindings: i2c: Add P8 OCC hwmon device documentation Eddie James
2018-11-08 21:05 ` [PATCH v6 05/10] hwmon: Add On-Chip Controller (OCC) hwmon driver Eddie James
2018-11-08 21:05 ` [PATCH v6 06/10] hwmon (occ): Add command transport method for P8 and P9 Eddie James
2018-11-08 21:05 ` [PATCH v6 07/10] hwmon (occ): Parse OCC poll response Eddie James
2018-11-08 21:05 ` [PATCH v6 08/10] hwmon (occ): Add sensor types and versions Eddie James
2018-11-08 21:05 ` [PATCH v6 09/10] hwmon (occ): Add sensor attributes and register hwmon device Eddie James
2018-11-08 21:05 ` [PATCH v6 10/10] hwmon (occ): Add sysfs attributes for additional OCC data Eddie James
2018-11-09 23:03 ` [PATCH v6 00/10] hwmon and fsi: Add On-Chip Controller Driver Guenter Roeck
2018-11-12 16:25 ` 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=1541711129-26631-2-git-send-email-eajames@linux.ibm.com \
--to=eajames@linux.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.vnet.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=jdelvare@suse.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=rdunlap@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.