From: Jerome Brunet <jbrunet@baylibre.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Jean Delvare <jdelvare@suse.com>,
Jonathan Corbet <corbet@lwn.net>,
Patrick Rudolph <patrick.rudolph@9elements.com>,
Naresh Solanki <naresh.solanki@9elements.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Delphine CC Chiu <Delphine_CC_Chiu@Wiwynn.com>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, devicetree@vger.kernel.org,
linux-i2c@vger.kernel.org,
Conor Dooley <conor.dooley@microchip.com>,
Vaishnav Achath <vaishnav.a@ti.com>
Subject: Re: [PATCH v4 0/7] hwmon: pmbus: add tps25990 efuse support
Date: Fri, 08 Nov 2024 09:52:51 +0100 [thread overview]
Message-ID: <1jldxu2jks.fsf@starbuckisacylon.baylibre.com> (raw)
In-Reply-To: <e88956d9-0dd1-4a38-8a91-8175223c87cc@roeck-us.net> (Guenter Roeck's message of "Wed, 6 Nov 2024 08:12:04 -0800")
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
--
Jerome
prev parent reply other threads:[~2024-11-08 8:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 17:58 [PATCH v4 0/7] hwmon: pmbus: add tps25990 efuse support Jerome Brunet
2024-11-05 17:58 ` [PATCH v4 1/7] hwmon: (pmbus) add documentation for existing flags Jerome Brunet
2024-11-06 15:57 ` Guenter Roeck
2024-11-05 17:58 ` [PATCH v4 2/7] hwmon: (pmbus/core) allow drivers to override WRITE_PROTECT Jerome Brunet
2024-11-06 15:58 ` Guenter Roeck
2024-11-05 17:58 ` [PATCH v4 3/7] hwmon: (pmbus/core) improve handling of write protected regulators Jerome Brunet
2024-11-05 17:58 ` [PATCH v4 4/7] hwmon: (pmbus/core) add wp module param Jerome Brunet
2024-11-05 17:58 ` [PATCH v4 5/7] hwmon: (pmbus/core) clear faults after setting smbalert mask Jerome Brunet
2024-11-06 16:03 ` Guenter Roeck
2024-11-05 17:58 ` [PATCH v4 6/7] dt-bindings: hwmon: pmbus: add ti tps25990 support Jerome Brunet
2024-11-06 16:05 ` Guenter Roeck
2024-11-05 17:58 ` [PATCH v4 7/7] hwmon: (pmbus/tps25990): add initial support Jerome Brunet
2024-11-06 18:59 ` Guenter Roeck
2024-11-08 8:47 ` Jerome Brunet
2024-11-06 16:12 ` [PATCH v4 0/7] hwmon: pmbus: add tps25990 efuse support Guenter Roeck
2024-11-08 8:52 ` Jerome Brunet [this message]
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=1jldxu2jks.fsf@starbuckisacylon.baylibre.com \
--to=jbrunet@baylibre.com \
--cc=Delphine_CC_Chiu@Wiwynn.com \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=krzk+dt@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=naresh.solanki@9elements.com \
--cc=patrick.rudolph@9elements.com \
--cc=robh@kernel.org \
--cc=vaishnav.a@ti.com \
/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