Message ID | 20241105-tps25990-v4-0-0e312ac70b62@baylibre.com (mailing list archive) |
---|---|
Headers | show |
Series | hwmon: pmbus: add tps25990 efuse support | expand |
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
On Wed 06 Nov 2024 at 08:12, Guenter Roeck <linux@roeck-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