From: Joel Stanley <joel@jms.id.au>
To: Rob Herring <robh+dt@kernel.org>,
Eddie James <eajames@linux.ibm.com>,
Guenter Roeck <linux@roeck-us.net>,
Andrew Jeffery <andrew@aj.id.au>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-hwmon@vger.kernel.org, linux-fsi@lists.ozlabs.org
Subject: [PATCH v2 0/3] occ: Add support for P10
Date: Fri, 20 Nov 2020 11:33:12 +1030 [thread overview]
Message-ID: <20201120010315.190737-1-joel@jms.id.au> (raw)
Hi Guenter, here's v2 of this series on behalf of Eddie. I made the
change to the compatible string that we spoke about in v2, and I'm happy
for these to go through the hwmon tree.
v1: https://lore.kernel.org/linux-hwmon/20200501150833.5251-1-eajames@linux.ibm.com/
The OCC in the P10 has a number of differences from the P9. Add some logic to
handle the differences in accessing the OCC from the service processor, and
support the new temperature sensor type.
Eddie James (3):
dt-bindings: fsi: Add P10 OCC device documentation
fsi: occ: Add support for P10
hwmon: (occ) Add new temperature sensor type
.../devicetree/bindings/fsi/ibm,p9-occ.txt | 12 +-
drivers/fsi/fsi-occ.c | 125 +++++++++++++-----
drivers/hwmon/occ/common.c | 75 +++++++++++
3 files changed, 172 insertions(+), 40 deletions(-)
--
2.29.2
next reply other threads:[~2020-11-20 1:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 1:03 Joel Stanley [this message]
2020-11-20 1:03 ` [PATCH v2 1/3] dt-bindings: fsi: Add P10 OCC device documentation Joel Stanley
2020-12-07 22:13 ` Rob Herring
2020-11-20 1:03 ` [PATCH v2 2/3] fsi: occ: Add support for P10 Joel Stanley
2020-11-20 1:03 ` [PATCH v2 3/3] hwmon: (occ) Add new temperature sensor type Joel Stanley
2020-11-21 18:51 ` [PATCH v2 0/3] occ: Add support for P10 Guenter Roeck
2020-12-08 2:41 ` Joel Stanley
2020-12-08 4:50 ` Guenter Roeck
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=20201120010315.190737-1-joel@jms.id.au \
--to=joel@jms.id.au \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.ibm.com \
--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 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.