From: Conor Dooley <conor@kernel.org>
To: "André Svensson" <andre.svensson@axis.com>
Cc: Support Opensource <support.opensource@diasemi.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>,
Adam Ward <Adam.Ward.opensource@diasemi.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
kernel@axis.com, Waqar Hameed <waqar.hameed@axis.com>
Subject: Re: [PATCH v2 1/2] regulator: dt-bindings: dlg,da9121: Add dlg,no-gpio-control
Date: Fri, 20 Mar 2026 17:57:53 +0000 [thread overview]
Message-ID: <20260320-banking-aerobics-7f32ef819d1a@spud> (raw)
In-Reply-To: <20260320-no-gpio-control-v2-1-dbc938e462cb@axis.com>
[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]
On Fri, Mar 20, 2026 at 08:33:24AM +0100, André Svensson wrote:
> Add the optional boolean property dlg,no-gpio-control. When present, it
> indicates that no DA91xx GPIO pins are configured/used with functions
> RELOAD/DVC/EN, which can affect the output voltage control, regulator
> mode control and enable signal control.
>
> The absence of relevant GPIO DT properties does not imply that the
> RELOAD/DVC/EN GPIO functions are unused. These functions are provided by
> DA91xx GPIO pins and may be controlled by external hardware without
> corresponding GPIO DT properties. The dlg,no-gpio-control property
> explicitly indicates that none of these GPIO functions are used.
>
> It is mutually exclusive with enable-gpios, regardless of whether the
> referenced GPIO is connected to a GPIO pin or the IC_EN pin, since
> enable-gpios allows the regulator to be controlled via an external
> hardware signal.
>
> Co-developed-by: Waqar Hameed <waqar.hameed@axis.com>
> Signed-off-by: Waqar Hameed <waqar.hameed@axis.com>
> Signed-off-by: André Svensson <andre.svensson@axis.com>
Acked-by: Conor Dooley <conor.dooley@microchip.com>
pw-bot: not-applicable
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next parent reply other threads:[~2026-03-20 17:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260320-no-gpio-control-v2-0-dbc938e462cb@axis.com>
[not found] ` <20260320-no-gpio-control-v2-1-dbc938e462cb@axis.com>
2026-03-20 17:57 ` Conor Dooley [this message]
2026-03-24 19:40 ` [PATCH v2 0/2] Allow caching of buck registers when no GPIO input control is configured 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=20260320-banking-aerobics-7f32ef819d1a@spud \
--to=conor@kernel.org \
--cc=Adam.Ward.opensource@diasemi.com \
--cc=andre.svensson@axis.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@axis.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=support.opensource@diasemi.com \
--cc=waqar.hameed@axis.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