Devicetree
 help / color / mirror / Atom feed
From: "Pradhan, Sanman" <sanman.pradhan@hpe.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Jonathan Corbet <corbet@lwn.net>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	"linux-hwmon@vger.kernel.org" <linux-hwmon@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	Sanman Pradhan <psanman@juniper.net>
Subject: [PATCH 0/2] hwmon: (pmbus/tps53679) Select page 0 for single-page parts
Date: Wed, 16 Sep 2026 20:04:02 +0000	[thread overview]
Message-ID: <20260916200331.664795-1-sanman.pradhan@hpe.com> (raw)

From: Sanman Pradhan <psanman@juniper.net>

For single-page TPS53676 and TPS536C7 configurations the PAGE register is
never normalised: pmbus_set_page() only writes PAGE when info->pages > 1,
so a page left selected by the boot firmware persists and telemetry is
read from the wrong page. Select page 0 explicitly (with readback) in the
two identify routines.

Patch 1 is a pre-existing TPS53676 fix (Fixes/stable). Patch 2 fixes the
TPS536C7 support and applies on top of the TPS53622/TPS53659/TPS536C7
series already applied to hwmon-next; it is not yet in a released kernel,
so it carries no stable tag.

These two patches apply on top of the TPS536C7 series ("hwmon:
(pmbus/tps53679) Add support for TPS536C7") already in hwmon-next, so
there is no separate base-commit line.

Link: https://lore.kernel.org/linux-hwmon/20260915164823.160977-1-sanman.pradhan@hpe.com/T/#t

Sanman Pradhan (2):
  hwmon: (pmbus/tps53679) Select page 0 for single-page TPS53676
  hwmon: (pmbus/tps53679) Select page 0 for single-page TPS536C7

 drivers/hwmon/pmbus/tps53679.c | 48 ++++++++++++++++++++++++++++++++++
 1 file changed, 48 insertions(+)

-- 
2.34.1


             reply	other threads:[~2026-09-16 20:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-16 20:04 Pradhan, Sanman [this message]
2026-09-16 20:04 ` [PATCH 1/2] hwmon: (pmbus/tps53679) Select page 0 for single-page TPS53676 Pradhan, Sanman
2026-09-16 21:41   ` Guenter Roeck
2026-09-16 23:06     ` Pradhan, Sanman
2026-09-16 20:04 ` [PATCH 2/2] hwmon: (pmbus/tps53679) Select page 0 for single-page TPS536C7 Pradhan, Sanman

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=20260916200331.664795-1-sanman.pradhan@hpe.com \
    --to=sanman.pradhan@hpe.com \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=psanman@juniper.net \
    --cc=robh@kernel.org \
    --cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox