From: Krzysztof Kozlowski <krzk@kernel.org>
To: Martijn de Gouw <martijn.de.gouw@prodrive-technologies.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Robin Gong <yibin.gong@nxp.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: regulator: add pca9450: Add regulator-allowed-modes
Date: Wed, 4 Jun 2025 10:27:55 +0200 [thread overview]
Message-ID: <5ea091c6-7e78-4945-81b4-9b5c427d2e4d@kernel.org> (raw)
In-Reply-To: <aced65a2-937e-494d-a3bd-aa9b295f73b7@prodrive-technologies.com>
On 04/06/2025 09:04, Martijn de Gouw wrote:
> Hi,
>
> On 5/25/2025 9:18 AM, Martijn de Gouw wrote:
>> Make the PWM mode on the buck controllers configurable from devicetree.
>> Some boards require forced PWM mode to keep the supply ripple within
>> acceptable limits under light load conditions.
>>
>> Signed-off-by: Martijn de Gouw <martijn.de.gouw@prodrive-technologies.com>
>> ---
>> Changes in v3:
>> - Fix typo in the examples
>> Changes in v2:
>> - Add the header to the binding patch
>> - Improve commit message
>>
>> .../regulator/nxp,pca9450-regulator.yaml | 14 ++++++++++++++
>> .../regulator/nxp,pca9450-regulator.h | 18 ++++++++++++++++++
>> 2 files changed, 32 insertions(+)
>
> Does this patch need additional changes?
What is wrong with the email you already received? What do you exactly
need from us?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-06-04 8:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-25 7:18 [PATCH v3 1/2] dt-bindings: regulator: add pca9450: Add regulator-allowed-modes Martijn de Gouw
2025-05-26 15:22 ` Conor Dooley
2025-06-04 7:04 ` Martijn de Gouw
2025-06-04 8:27 ` Krzysztof Kozlowski [this message]
2025-06-04 8:58 ` Martijn de Gouw
2025-06-04 9:07 ` Krzysztof Kozlowski
2025-06-04 9:10 ` Martijn de Gouw
2025-06-09 13:00 ` Mark Brown
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=5ea091c6-7e78-4945-81b4-9b5c427d2e4d@kernel.org \
--to=krzk@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martijn.de.gouw@prodrive-technologies.com \
--cc=robh@kernel.org \
--cc=yibin.gong@nxp.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