From: Eddie James <eajames@linux.ibm.com>
To: joel@jms.id.au
Cc: linux@roeck-us.net, jdelvare@suse.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, linux-kernel@vger.kernel.org,
linux-hwmon@vger.kernel.org, linux-fsi@lists.ozlabs.org,
devicetree@vger.kernel.org, Eddie James <eajames@linux.ibm.com>
Subject: [PATCH 1/3] dt-bindings: hwmon: Add IBM OCC bindings
Date: Tue, 2 Aug 2022 14:46:54 -0500 [thread overview]
Message-ID: <20220802194656.240564-2-eajames@linux.ibm.com> (raw)
In-Reply-To: <20220802194656.240564-1-eajames@linux.ibm.com>
These bindings describe the POWER processor On Chip Controller accessed
from a service processor or baseboard management controller (BMC).
Signed-off-by: Eddie James <eajames@linux.ibm.com>
---
.../bindings/hwmon/ibm,occ-hmwon.yaml | 40 +++++++++++++++++++
1 file changed, 40 insertions(+)
create mode 100644 Documentation/devicetree/bindings/hwmon/ibm,occ-hmwon.yaml
diff --git a/Documentation/devicetree/bindings/hwmon/ibm,occ-hmwon.yaml b/Documentation/devicetree/bindings/hwmon/ibm,occ-hmwon.yaml
new file mode 100644
index 000000000000..8f8c3b8d7129
--- /dev/null
+++ b/Documentation/devicetree/bindings/hwmon/ibm,occ-hmwon.yaml
@@ -0,0 +1,40 @@
+# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/hwmon/ibm,occ-hwmon.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: IBM On-Chip Controller (OCC) accessed from a service processor
+
+maintainers:
+ - Eddie James <eajames@linux.ibm.com>
+
+description: |
+ This binding describes a POWER processor On-Chip Controller (OCC)
+ accessed from a service processor or baseboard management controller
+ (BMC).
+
+properties:
+ compatible:
+ enum:
+ - ibm,p9-occ-hwmon
+ - ibm,p10-occ-hwmon
+
+ ibm,inactive-on-init:
+ description: This property describes whether or not the OCC should
+ be marked as active during device initialization. The alternative
+ is for user space to mark the device active based on higher level
+ communications between the BMC and the host processor.
+ type: boolean
+
+required:
+ - compatible
+
+additionalProperties: false
+
+examples:
+ - |
+ occ-hmwon {
+ compatible = "ibm,p9-occ-hwmon";
+ ibm,inactive-on-init;
+ };
--
2.31.1
next prev parent reply other threads:[~2022-08-02 19:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 19:46 [PATCH 0/3] occ: Restore default behavior of polling OCC during init Eddie James
2022-08-02 19:46 ` Eddie James [this message]
2022-08-02 22:38 ` [PATCH 1/3] dt-bindings: hwmon: Add IBM OCC bindings Rob Herring
2022-08-03 6:55 ` Krzysztof Kozlowski
2022-08-09 19:42 ` Eddie James
2022-08-10 7:43 ` Krzysztof Kozlowski
2022-08-10 13:56 ` Eddie James
2022-08-02 19:46 ` [PATCH 2/3] fsi: occ: Support probing the hwmon child device from dts node Eddie James
2022-08-02 19:46 ` [PATCH 3/3] hwmon: (occ) Check for device property for setting OCC active during probe Eddie James
2022-08-03 12:21 ` kernel test robot
2022-08-03 14:44 ` kernel 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=20220802194656.240564-2-eajames@linux.ibm.com \
--to=eajames@linux.ibm.com \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-fsi@lists.ozlabs.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--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).