From: sashiko-bot@kernel.org
To: "Pradhan, Sanman" <sanman.pradhan@hpe.com>
Cc: conor+dt@kernel.org, linux-hwmon@vger.kernel.org,
robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 3/3] hwmon: (pmbus/tps53679) Add support for TPS536C7
Date: Tue, 15 Sep 2026 16:57:37 +0000 [thread overview]
Message-ID: <20260915165738.31BF61F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260915164823.160977-4-sanman.pradhan@hpe.com>
> From: Sanman Pradhan <psanman@juniper.net>
>
> TPS536C7 is a dual-channel D-CAP+ step-down controller whose channels are
> distributed across a configurable number of phases (N+M, up to 12 total).
> Whether channel B (PMBus page 1) exists depends on the phase configuration
> register, so the page count is derived at probe time.
>
> Factor the TPS53676 phase-map parsing into a shared helper and reuse it
> for TPS536C7. Only aggregate per-channel telemetry is exposed: leave
> info->phases[] unset so the PMBus core never programs the PHASE selector
> on every read (and because TPS536C7 can place up to 12 phases on channel
> A, exceeding PMBUS_PHASES). Report VOUT in linear format like TPS53676.
>
> Since the core never programs PHASE, set it to 0xff on each populated
> page so READ_IOUT reports the aggregate channel current, and verify it
> [ ... ]
> so only those two identification reads fall back to no-PEC.
>
> Co-developed-by: Senthil Muniyappan <smuniyappan@juniper.net>
> Co-developed-by: Vaibhav Agarwal <avaibhav@juniper.net>
> Signed-off-by: Sanman Pradhan <psanman@juniper.net>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260915164823.160977-1-sanman.pradhan@hpe.com?part=3
next prev parent reply other threads:[~2026-09-15 16:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 16:48 [PATCH v2 0/3] hwmon: (pmbus/tps53679) Add TPS536C7 Pradhan, Sanman
2026-09-15 16:48 ` [PATCH v2 1/3] hwmon: (pmbus/tps53679) Fix TPS53676 phase page decoding Pradhan, Sanman
2026-09-15 16:53 ` sashiko-bot
2026-09-15 17:31 ` Guenter Roeck
2026-09-16 14:56 ` Guenter Roeck
2026-09-16 17:46 ` Pradhan, Sanman
2026-09-16 17:59 ` Guenter Roeck
2026-09-16 18:44 ` Pradhan, Sanman
2026-09-15 16:48 ` [PATCH v2 2/3] dt-bindings: trivial-devices: Add TI TPS536C7 Pradhan, Sanman
2026-09-15 16:52 ` sashiko-bot
2026-09-16 14:57 ` Guenter Roeck
2026-09-15 16:48 ` [PATCH v2 3/3] hwmon: (pmbus/tps53679) Add support for TPS536C7 Pradhan, Sanman
2026-09-15 16:57 ` sashiko-bot [this message]
2026-09-16 14:59 ` 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=20260915165738.31BF61F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sanman.pradhan@hpe.com \
--cc=sashiko-reviews@lists.linux.dev \
/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