From: Krzysztof Kozlowski <krzk@kernel.org>
To: Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Robin Gong <yibin.gong@nxp.com>,
Martijn de Gouw <martijn.de.gouw@prodrive-technologies.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: regulator: add pca9450: Add regulator-allowed-modes
Date: Sat, 24 May 2025 08:34:41 +0200 [thread overview]
Message-ID: <8ff817a3-c734-45de-afbd-5da9aecd4cbb@kernel.org> (raw)
In-Reply-To: <174801730004.578098.7742808995079543725.b4-ty@kernel.org>
On 23/05/2025 18:21, Mark Brown wrote:
> On Fri, 23 May 2025 15:12:11 +0200, 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.
>>
>>
>
> Applied to
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
>
> Thanks!
>
> [1/2] dt-bindings: regulator: add pca9450: Add regulator-allowed-modes
> commit: 0a4056a444c8d55beea470948c73befd6673aa6c
> [2/2] regulator: pca9450: Add support for mode operations
> commit: 2616e5f4fe04eb25eb5cbabc0a3a2a374e14008e
Rob reported binding has failure (which also means binding was not
tested). Can you drop the patch?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-05-24 6:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 13:12 [PATCH v2 1/2] dt-bindings: regulator: add pca9450: Add regulator-allowed-modes Martijn de Gouw
2025-05-23 14:01 ` Mark Brown
2025-05-23 14:23 ` Rob Herring (Arm)
2025-05-23 16:21 ` Mark Brown
2025-05-24 6:34 ` Krzysztof Kozlowski [this message]
2025-05-24 22:38 ` Mark Brown
2025-05-25 4:43 ` Krzysztof Kozlowski
2025-05-25 11:50 ` 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=8ff817a3-c734-45de-afbd-5da9aecd4cbb@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