From: Guenter Roeck <linux@roeck-us.net>
To: ashish yadav <ashishyadav78@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
ASHISH YADAV <Ashish.Yadav@infineon.com>
Subject: Re: [PATCH v2 1/2] hwmon:(pmbus/tda38740a) TDA38740A Voltage Regulator Driver
Date: Sun, 1 Feb 2026 16:29:38 -0800 [thread overview]
Message-ID: <787ffcff-28cb-43e0-97db-19dd7a996d13@roeck-us.net> (raw)
In-Reply-To: <CAJKbuCYUCr-R-91Ou1y6XDEPdqabSDvCxUypc-YmW=-EPxgNyQ@mail.gmail.com>
On 1/22/26 03:42, ashish yadav wrote:
> Hi Guenter,
>
> Please find my response inline.
>
> Thanks & Regards
> Ashish Yadav
>
> On Tue, Jan 13, 2026 at 8:40 PM Guenter Roeck <linux@roeck-us.net> wrote:
>>
>> On 1/12/26 23:24, ashish yadav wrote:
>>
>>>> The need for this, especially why it would only be needed for PMBUS_READ_VOUT
>>>> but not for any other VOUT related commands, is still insufficiently explained
>>>> (and I failed to understand the rationale provided earlier).
>>>>
>>>
>>> It is specifically needed for READ_VOUT as it is being used by
>>> external controller to monitor the rail health.
>>> Other Vout related parameters are used internally in the IC to for
>>> output voltage related protections and does not impact any external
>>> decision making.
>>>
>>
>> Sorry, that doesn't really make sense. How would the chip know to match
>> VOUT with its VOUT limits if both don't use the same scale ?
>>
> The chip telemetry would still show Vout as 0.7V as it does not know
> about the external feedback resistors.
> Hence, no need to scale internal Vout related parameters.
> This scale is only for external vendor use to tweak their telemetry
> output voltage reading.
>
You fail to explain why VOUT_SCALE_LOOP - which is supposed to handle such
situations - can not be used, and why it would be acceptable for other VOUT
related attributes such as VOUT_MIN, VOUT_MAX, VOUT_MARGIN_LOW, VOUT_MARGIN_HIGH,
and the various VOUT fault limits to show the wrong values.
For reference:
VOUT_SCALE_LOOP:
"Used to account for any external attenuation network on VOUT sense
feedback and provide correct VOUT reporting."
Guenter
next prev parent reply other threads:[~2026-02-02 0:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 14:45 ASHISH YADAV
2026-01-07 14:45 ` [PATCH v2 2/2] dt-bindings: hwmon/pmbus: Add Infineon TDA38740A ASHISH YADAV
2026-01-07 16:14 ` Krzysztof Kozlowski
2026-01-08 9:24 ` ashish yadav
2026-01-08 8:54 ` Krzysztof Kozlowski
2026-01-08 9:17 ` ashish yadav
2026-01-12 21:42 ` Guenter Roeck
2026-01-13 7:27 ` ashish yadav
2026-01-09 16:23 ` [PATCH v2 1/2] hwmon:(pmbus/tda38740a) TDA38740A Voltage Regulator Driver ashish yadav
2026-01-12 21:51 ` Guenter Roeck
2026-01-13 7:24 ` ashish yadav
2026-01-13 15:10 ` Guenter Roeck
2026-01-22 11:42 ` ashish yadav
2026-02-02 0:29 ` Guenter Roeck [this message]
2026-02-09 5:04 ` ashish yadav
2026-02-09 16:09 ` 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=787ffcff-28cb-43e0-97db-19dd7a996d13@roeck-us.net \
--to=linux@roeck-us.net \
--cc=Ashish.Yadav@infineon.com \
--cc=ashishyadav78@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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
all inboxes | Powered by JetHome®