From: "Cédric Le Goater" <clg@fr.ibm.com>
To: lm-sensors@lm-sensors.org
Cc: "Stewart Smith" <stewart@linux.vnet.ibm.com>,
"Cédric Le Goater" <clg@fr.ibm.com>,
"Jean Delvare" <jdelvare@suse.de>,
"Neelesh Gupta" <neelegup@linux.vnet.ibm.com>,
skiboot@lists.ozlabs.org, linuxppc-dev@lists.ozlabs.org,
"Guenter Roeck" <linux@roeck-us.net>
Subject: [PATCH v5 0/4] hwmon: (ibmpowernv) add DTS support
Date: Wed, 8 Apr 2015 19:19:46 +0200 [thread overview]
Message-ID: <1428513590-5773-1-git-send-email-clg@fr.ibm.com> (raw)
Hello !
These patches extend the ibmpowernv driver to support the new OPAL firmware
which now exposes in its device tree the Digital Temperature Sensors of
a P8 system.
They are based on Linux 4.0.0-rc7 + the initial cleanup serie :
http://lists.lm-sensors.org/pipermail/lm-sensors/2015-March/043670.html
and were tested on IBM Power and Open Power systems running Trusty.
Cheers,
C.
Changes since v4:
- fixed comparison between signed and unsigned integer in
get_logical_cpu()
Changes since v3:
- removed error message in case of an unknown physical cpu number
Changes since v2:
- fix bogus logical cpu retrieval
- use 'threads_per_core' to print out cpu range
Changes since v1:
- check cpu validity before printing out the attribute label.
if invalid, use a "phy" prefix to distinguish a linux cpu
number from a physical cpu number.
- fixed alignment
- fixed comparison between signed and unsigned integer on opal_index
Cédric Le Goater (4):
hwmon: (ibmpowernv) add a helper routine create_hwmon_attr
hwmon: (ibmpowernv) add support for the new device tree
hwmon: (ibmpowernv) add a label attribute
hwmon: (ibmpowernv) pretty print labels
drivers/hwmon/ibmpowernv.c | 166 +++++++++++++++++++++++++++++++++++++++-----
1 file changed, 148 insertions(+), 18 deletions(-)
--
1.7.10.4
next reply other threads:[~2015-04-08 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 17:19 Cédric Le Goater [this message]
2015-04-08 17:32 ` [PATCH v5 0/4] hwmon: (ibmpowernv) add DTS support Guenter Roeck
2015-04-08 17:33 ` Cedric Le Goater
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=1428513590-5773-1-git-send-email-clg@fr.ibm.com \
--to=clg@fr.ibm.com \
--cc=jdelvare@suse.de \
--cc=linux@roeck-us.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lm-sensors@lm-sensors.org \
--cc=neelegup@linux.vnet.ibm.com \
--cc=skiboot@lists.ozlabs.org \
--cc=stewart@linux.vnet.ibm.com \
/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).