[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1jldxu2jks.fsf@starbuckisacylon.baylibre.com>
Date: Fri, 08 Nov 2024 09:52:51 +0100
From: Jerome Brunet <jbrunet@...libre.com>
To: Guenter Roeck <linux@...ck-us.net>
Cc: 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>,
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 Wed 06 Nov 2024 at 08:12, Guenter Roeck <linux@...ck-us.net> wrote:
> 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.
These 2 patches where always gonna be touching the same part of the
code. Indeed 4 could have come before, I did not really think about it
TBH.
No problem waiting for -rc1. I'll rebase the remaining changes when it's
out and add the necessary change on patch 7.
Thanks for your support
>
> Guenter
--
Jerome
Powered by blists - more mailing lists