From: Eddie James <eajames@linux.ibm.com>
To: linux-hwmon@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, jdelvare@suse.com,
linux@roeck-us.net, eajames@linux.ibm.com, bjwyman@gmail.com
Subject: [PATCH 0/2] hwmon: (pmbus) Add a NO_PEC flag to probe chips with faulty CAPABILITY
Date: Mon, 21 Dec 2020 10:30:56 -0600 [thread overview]
Message-ID: <20201221163058.33257-1-eajames@linux.ibm.com> (raw)
Some PMBus chips don't respond with valid data when reading the
CAPABILITY register. For instance the register may report that the
chip supports PEC when in reality it does not. For such chips, PEC
must not be enabled while probing the chip, so this series adds a flag
that allows device drivers to force PEC off. The second patch enables
this flag for the IBM CFFPS driver, which supports power supplies that
report invalid in the CAPABILITY register and must therefore force PEC
off.
Eddie James (2):
hwmon: (pmbus) Add a NO_PEC flag to probe chips with faulty CAPABILITY
hwmon: (pmbus/ibm-cffps) Set the PMBUS_NO_PEC flag
drivers/hwmon/pmbus/ibm-cffps.c | 2 +-
drivers/hwmon/pmbus/pmbus_core.c | 8 +++++---
include/linux/pmbus.h | 10 ++++++++++
3 files changed, 16 insertions(+), 4 deletions(-)
--
2.27.0
next reply other threads:[~2020-12-21 16:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 16:30 Eddie James [this message]
2020-12-21 16:30 ` [PATCH 1/2] hwmon: (pmbus) Add a NO_PEC flag to probe chips with faulty CAPABILITY Eddie James
2020-12-21 16:54 ` Guenter Roeck
2020-12-21 18:32 ` Eddie James
2020-12-21 18:53 ` Guenter Roeck
2020-12-21 16:30 ` [PATCH 2/2] hwmon: (pmbus/ibm-cffps) Set the PMBUS_NO_PEC flag 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=20201221163058.33257-1-eajames@linux.ibm.com \
--to=eajames@linux.ibm.com \
--cc=bjwyman@gmail.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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