public inbox for linux-hwmon@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Hardware Monitoring <linux-hwmon@vger.kernel.org>
Cc: Sanman Pradhan <psanman@juniper.net>, Guenter Roeck <linux@roeck-us.net>
Subject: [PATCH 0/5] hwmon: (pmbus) PMBus fixes and improvements
Date: Wed, 25 Mar 2026 11:16:26 -0700	[thread overview]
Message-ID: <20260325181631.17259-1-linux@roeck-us.net> (raw)

The first patch of the series marks lowest/average/highest/rated attributes
as read-only. Those are values provided by the chip and must not be
modified during runtime (if that is even supported by the chip).

The second patch adds support for write-only attributes. As it turned out,
reading the "reset_history" attributes returned random values. The code now
returns 0 when reading those attributes to avoid ABI hiccups.

The third patch adds locking for regulator operations to avoid interference
with other PMBus operations.

The last two patches introduce and start using guard() and scoped_guard()
for PMBus locking to simplify the code, especially for error handling.

Change log since RFT/RFC: All patches were tested with real hardware.

----------------------------------------------------------------
Guenter Roeck (5):
      hwmon: (pmbus) Mark lowest/average/highest/rated attributes as read-only
      hwmon: (pmbus) Introduce the concept of "write-only" attributes
      hwmon: (pmbus/core) Protect regulator operations with mutex
      hwmon: (pmbus) Add support for guarded PMBus lock
      hwmon: (pmbus_core) Use guard() for mutex protection

 drivers/hwmon/pmbus/pmbus.h      |   5 +
 drivers/hwmon/pmbus/pmbus_core.c | 373 +++++++++++++++++++++++----------------
 2 files changed, 222 insertions(+), 156 deletions(-)

             reply	other threads:[~2026-03-25 18:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-25 18:16 Guenter Roeck [this message]
2026-03-25 18:16 ` [PATCH 1/5] hwmon: (pmbus) Mark lowest/average/highest/rated attributes as read-only Guenter Roeck
2026-03-25 18:16 ` [PATCH 2/5] hwmon: (pmbus) Introduce the concept of "write-only" attributes Guenter Roeck
2026-03-25 18:16 ` [PATCH 3/5] hwmon: (pmbus/core) Protect regulator operations with mutex Guenter Roeck
2026-03-25 19:05   ` Pradhan, Sanman
2026-03-25 20:02     ` Guenter Roeck
2026-03-25 18:16 ` [PATCH 4/5] hwmon: (pmbus) Add support for guarded PMBus lock Guenter Roeck
2026-03-25 18:16 ` [PATCH 5/5] hwmon: (pmbus_core) Use guard() for mutex protection Guenter Roeck
2026-03-25 20:25 ` [PATCH 0/5] hwmon: (pmbus) PMBus fixes and improvements Pradhan, Sanman
2026-03-25 20:31   ` 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=20260325181631.17259-1-linux@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=psanman@juniper.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