From: Guenter Roeck <linux@roeck-us.net>
To: Patryk Biel <pbiel7@gmail.com>
Cc: Jean Delvare <jdelvare@suse.com>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwmon: Conditionally clear individual status bits for pmbus rev >= 1.2
Date: Mon, 9 Sep 2024 10:59:43 -0700 [thread overview]
Message-ID: <9f6fd5f4-ded1-456e-b4ee-264eed09b867@roeck-us.net> (raw)
In-Reply-To: <20240909-pmbus-status-reg-clearing-v1-1-f1c0d68c6408@gmail.com>
On Mon, Sep 09, 2024 at 11:30:28AM +0200, Patryk Biel wrote:
> This change adds fetching PMBus revision and using it to conditionally
> clear individual status bits while calling pmbus_show_boolean, only if
> the device is compliant with PMBus specs >= 1.2.
>
> Signed-off-by: Patryk Biel <pbiel7@gmail.com>
> ---
> Current implementation of pmbus_show_boolean assumes that all devices
> support write-back operation of status register so as to clear pending
> warning or faults. Since clearing individual bits in the status registers
> was introduced in PMBus specification 1.2, this operation may not be
> supported by some older devices, thus resulting in error while reading
> boolean attributes like e.g. temp1_max_alarm.
>
> This change adds fetching PMBus revision supported by device and
> modifies pmbus_show_boolean so that it only tries to clear individual
> status bits if the device is compilant with PMBus specs >= 1.2.
>
> Tested on: LTC2971, LTC2971-1, LTC2974, LTC2977.
> ---
> drivers/hwmon/pmbus/pmbus.h | 6 ++++++
> drivers/hwmon/pmbus/pmbus_core.c | 12 +++++++++++-
> 2 files changed, 17 insertions(+), 1 deletion(-)
>
>
> ---
> base-commit: c763c43396883456ef57e5e78b64d3c259c4babc
> change-id: 20240905-pmbus-status-reg-clearing-abc9c0184c3b
>
> Best regards,
>
> diff --git a/drivers/hwmon/pmbus/pmbus.h b/drivers/hwmon/pmbus/pmbus.h
> index fb442fae7b3e..0bea603994e7 100644
> --- a/drivers/hwmon/pmbus/pmbus.h
> +++ b/drivers/hwmon/pmbus/pmbus.h
> @@ -418,6 +418,12 @@ enum pmbus_sensor_classes {
> enum pmbus_data_format { linear = 0, ieee754, direct, vid };
> enum vrm_version { vr11 = 0, vr12, vr13, imvp9, amd625mv };
>
> +/* PMBus revision identifiers */
> +#define PMBUS_REV_10 0x00 /* PMBus revision 1.0 */
> +#define PMBUS_REV_11 0x11 /* PMBus revision 1.1 */
> +#define PMBUS_REV_12 0x22 /* PMBus revision 1.2 */
> +#define PMBUS_REV_13 0x33 /* PMBus revision 1.3 */
> +
> struct pmbus_driver_info {
> int pages; /* Total number of pages */
> u8 phases[PMBUS_PAGES]; /* Number of phases per page */
> diff --git a/drivers/hwmon/pmbus/pmbus_core.c b/drivers/hwmon/pmbus/pmbus_core.c
> index cb4c65a7f288..50ba093a38e8 100644
> --- a/drivers/hwmon/pmbus/pmbus_core.c
> +++ b/drivers/hwmon/pmbus/pmbus_core.c
> @@ -108,6 +108,8 @@ struct pmbus_data {
>
> int vout_low[PMBUS_PAGES]; /* voltage low margin */
> int vout_high[PMBUS_PAGES]; /* voltage high margin */
> +
> + u8 revision; /* The PMBus revision the device is compliant with */
> };
>
> struct pmbus_debugfs_entry {
> @@ -1095,7 +1097,11 @@ static int pmbus_get_boolean(struct i2c_client *client, struct pmbus_boolean *b,
>
> regval = status & mask;
> if (regval) {
> - ret = _pmbus_write_byte_data(client, page, reg, regval);
> + if (data->revision >= PMBUS_REV_12)
> + ret = _pmbus_write_byte_data(client, page, reg, regval);
> + else
> + pmbus_clear_fault_page(client, page);
> +
> if (ret)
> goto unlock;
That check needs to be part of the if() statement above. Never mind, though,
I fixed that up.
Guenter
next prev parent reply other threads:[~2024-09-09 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 9:30 [PATCH] hwmon: Conditionally clear individual status bits for pmbus rev >= 1.2 Patryk Biel
2024-09-09 16:54 ` Guenter Roeck
2024-09-09 17:59 ` Guenter Roeck [this message]
2024-09-12 16:36 ` 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=9f6fd5f4-ded1-456e-b4ee-264eed09b867@roeck-us.net \
--to=linux@roeck-us.net \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbiel7@gmail.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