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] [thread-next>] [day] [month] [year] [list]
Message-ID: <e88956d9-0dd1-4a38-8a91-8175223c87cc@roeck-us.net>
Date: Wed, 6 Nov 2024 08:12:04 -0800
From: Guenter Roeck <linux@...ck-us.net>
To: Jerome Brunet <jbrunet@...libre.com>, Jean Delvare <jdelvare@...e.com>,
 Jonathan Corbet <corbet@....net>,
 Patrick Rudolph <patrick.rudolph@...ements.com>,
 Naresh Solanki <naresh.solanki@...ements.com>, Rob Herring
 <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Conor Dooley <conor+dt@...nel.org>,
 Delphine CC Chiu <Delphine_CC_Chiu@...ynn.com>
Cc: linux-hwmon@...r.kernel.org, linux-kernel@...r.kernel.org,
 linux-doc@...r.kernel.org, devicetree@...r.kernel.org,
 linux-i2c@...r.kernel.org, Conor Dooley <conor.dooley@...rochip.com>,
 Vaishnav Achath <vaishnav.a@...com>
Subject: Re: [PATCH v4 0/7] hwmon: pmbus: add tps25990 efuse support

On 11/5/24 09:58, Jerome Brunet wrote:
> This patchset adds initial support for the Texas Instruments TPS25990
> eFuse. The TPS25990 is an integrated, high-current circuit protection and
> power management device. TPS25895 may be stacked on the TPS25990 for
> higher currents.
> 
> This patchset provides basic telemetry support for the device.
> On boot, the device is write protected. Limits can be changed in sysfs
> if the write protection is removed using the introduced pmbus parameter.
> 
> Limits will be restored to the default value device on startup, unless
> saved to NVM. Writing the NVM is not supported by the driver at the moment.
> 
> As part of this series, PMBus regulator support is improved to better
> support write-protected devices.
> 
> Patch 3 depends on the regulator patchset available here [1].
> This is a compilation dependency.
> 

Unfortunately this means that I can not apply this and the following patch
until after the next commit window, which is unfortunate since patch 4
does not logically depend on patch 3. That also means that I can not apply
the last patch of the series since it depends on the ability to disable
write protect. Those patches will have to wait until after the next commit
window.

Guenter


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ