mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "André Svensson" <andresve@axis.com>
To: "Mark Brown" <broonie@kernel.org>,
	"André Svensson" <andre.svensson@axis.com>
Cc: Support Opensource <support.opensource@diasemi.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	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 1/2] regulator: dt-bindings: dlg,da9121: Add dlg,no-gpio-control
Date: Tue, 10 Mar 2026 09:55:11 +0100	[thread overview]
Message-ID: <976e1ee5-bc3a-47ef-808d-014ad6ade533@axis.com> (raw)
In-Reply-To: <f5ee1e87-f4ef-46e1-a705-cba532e1db2e@sirena.org.uk>

On 3/9/26 5:30 PM, Mark Brown wrote:
> On Mon, Mar 09, 2026 at 04:52:35PM +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.
> 
>> 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.
> 
> This should probably explain why we can't infer the absence of GPIOs
> from the lack of any relevant GPIO properties.

Thanks, I’ll clarify that in v2.

  reply	other threads:[~2026-03-10  8:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09 15:52 [PATCH 0/2] Allow caching of buck registers when no GPIO input control is configured André Svensson
2026-03-09 15:52 ` [PATCH 1/2] regulator: dt-bindings: dlg,da9121: Add dlg,no-gpio-control André Svensson
2026-03-09 16:30   ` Mark Brown
2026-03-10  8:55     ` André Svensson [this message]
2026-03-09 15:52 ` [PATCH 2/2] regulator: da9121: Allow caching BUCK registers André Svensson

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=976e1ee5-bc3a-47ef-808d-014ad6ade533@axis.com \
    --to=andresve@axis.com \
    --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
all inboxes | Powered by JetHome®