From: Eddie James <eajames@linux.vnet.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,
openbmc@lists.ozlabs.org, robh+dt@kernel.org,
gregkh@linuxfoundation.org, mark.rutland@arm.com,
linux@roeck-us.net, joel@jms.id.au, benh@kernel.crashing.org,
Eddie James <eajames@linux.vnet.ibm.com>
Subject: [PATCH v5 01/10] dt-bindings: fsi: Add P9 OCC device documentation
Date: Thu, 30 Aug 2018 16:32:32 -0500 [thread overview]
Message-ID: <1535664761-86018-2-git-send-email-eajames@linux.vnet.ibm.com> (raw)
In-Reply-To: <1535664761-86018-1-git-send-email-eajames@linux.vnet.ibm.com>
Document the bindings for the FSI-attached POWER9 On-Chip Controller.
Signed-off-by: Eddie James <eajames@linux.vnet.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..46372f6
--- /dev/null
+++ b/Documentation/devicetree/bindings/fsi/ibm,p9-occ.txt
@@ -0,0 +1,15 @@
+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.
+
+Required properties:
+ - compatible = "ibm,p9-occ"
+
+Examples:
+
+ occ {
+ compatible = "ibm,p9-occ";
+ };
--
1.8.3.1
next prev parent reply other threads:[~2018-08-30 21:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 21:32 [PATCH v5 00/10] hwmon and fsi: Add On-Chip Controller Driver Eddie James
2018-08-30 21:32 ` Eddie James [this message]
2018-09-10 18:16 ` [PATCH v5 01/10] dt-bindings: fsi: Add P9 OCC device documentation Rob Herring
2018-09-12 7:56 ` Benjamin Herrenschmidt
2018-10-12 12:44 ` Guenter Roeck
2018-08-30 21:32 ` [PATCH v5 02/10] fsi: Add On-Chip Controller (OCC) driver Eddie James
2018-08-30 21:32 ` [PATCH v5 03/10] Documentation: hwmon: Add OCC documentation Eddie James
2018-08-31 23:01 ` Randy Dunlap
2018-08-30 21:32 ` [PATCH v5 04/10] dt-bindings: i2c: Add P8 OCC hwmon device documentation Eddie James
2018-08-30 21:32 ` [PATCH v5 05/10] hwmon: Add On-Chip Controller (OCC) hwmon driver Eddie James
2018-09-01 12:06 ` kbuild test robot
2018-10-12 12:46 ` Guenter Roeck
2018-08-30 21:32 ` [PATCH v5 06/10] hwmon (occ): Add command transport method for P8 and P9 Eddie James
2018-08-30 21:32 ` [PATCH v5 07/10] hwmon (occ): Parse OCC poll response Eddie James
2018-08-30 21:32 ` [PATCH v5 08/10] hwmon (occ): Add sensor types and versions Eddie James
2018-08-30 21:32 ` [PATCH v5 09/10] hwmon (occ): Add sensor attributes and register hwmon device Eddie James
2018-08-30 21:32 ` [PATCH v5 10/10] hwmon (occ): Add sysfs attributes for additional OCC data 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=1535664761-86018-2-git-send-email-eajames@linux.vnet.ibm.com \
--to=eajames@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jdelvare@suse.com \
--cc=joel@jms.id.au \
--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=openbmc@lists.ozlabs.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 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).