From: Neil Armstrong <neil.armstrong@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
KancyJoe <kancy2333@outlook.com>
Subject: Re: [PATCH 1/2] dt-bindings: regulator: document the SGM3804 Dual Output regulator
Date: Wed, 29 Apr 2026 10:02:29 +0200 [thread overview]
Message-ID: <164780ac-2e56-4169-b42a-1b06e592a303@linaro.org> (raw)
In-Reply-To: <afFTIlkS7Vg_2Eah@sirena.co.uk>
On 4/29/26 02:38, Mark Brown wrote:
> On Tue, Apr 28, 2026 at 03:52:05PM +0200, Neil Armstrong wrote:
>> Document the SG Micro SGM3804 Single Inductor Dual Output Buck/Boost
>> Converter used to power LCD panels a provide positive and negative
>> power rails with configurable voltage and active discharge function
>> for each output.
>
>> + enable-gpios:
>> + maxItems: 2
>> + description:
>> + GPIO specifiers to enable the positive and negative outputs.
>
> The driver requires both to be provided, either it should relax it's
> requirements during probe() and allow only one of the regulators to be
> instantiated or if that's not a realistic setup the binding should set
> minItems too.
It's a mismatch on my side, it needs both gpios, I'll fix it.
Neil
next prev parent reply other threads:[~2026-04-29 8:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 13:52 [PATCH 0/2] regulator: add support for SGM3804 Dual Output driver Neil Armstrong
2026-04-28 13:52 ` [PATCH 1/2] dt-bindings: regulator: document the SGM3804 Dual Output regulator Neil Armstrong
2026-04-28 15:30 ` Rob Herring (Arm)
2026-04-29 0:23 ` Mark Brown
2026-04-29 0:38 ` Mark Brown
2026-04-29 8:02 ` Neil Armstrong [this message]
2026-04-28 13:52 ` [PATCH 2/2] regulator: add SGM3804 Dual Output driver Neil Armstrong
2026-04-29 0:37 ` Mark Brown
2026-04-29 0:44 ` Mark Brown
2026-04-29 8:05 ` Neil Armstrong
2026-04-30 1:06 ` Mark Brown
2026-04-30 7:16 ` Neil Armstrong
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=164780ac-2e56-4169-b42a-1b06e592a303@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kancy2333@outlook.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
/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