lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f0d230be-676b-47b9-9565-22319b8e62cc@roeck-us.net>
Date: Tue, 13 Jan 2026 07:10:04 -0800
From: Guenter Roeck <linux@...ck-us.net>
To: ashish yadav <ashishyadav78@...il.com>
Cc: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Conor Dooley <conor+dt@...nel.org>, linux-hwmon@...r.kernel.org,
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
 ASHISH YADAV <Ashish.Yadav@...ineon.com>
Subject: Re: [PATCH v2 1/2] hwmon:(pmbus/tda38740a) TDA38740A Voltage
 Regulator Driver

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 ?

Guenter


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ