public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	linux-mediatek@lists.infradead.org, lee@kernel.org,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	matthias.bgg@gmail.com, lgirdwood@gmail.com,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, kernel@collabora.com,
	wenst@chromium.org, igor.belwon@mentallysanemainliners.org
Subject: Re: [PATCH v10 1/9] dt-bindings: regulator: Document MediaTek MT6316 PMIC Regulators
Date: Sun, 26 Oct 2025 22:21:54 +0000	[thread overview]
Message-ID: <20251026-despise-treadmill-12636f1a476f@spud> (raw)
In-Reply-To: <aPvETBr5aebElQUS@finisterre.sirena.org.uk>

[-- Attachment #1: Type: text/plain, Size: 1149 bytes --]

On Fri, Oct 24, 2025 at 07:24:12PM +0100, Mark Brown wrote:
> On Fri, Oct 24, 2025 at 05:29:31PM +0100, Conor Dooley wrote:
> > On Fri, Oct 24, 2025 at 10:32:13AM +0200, AngeloGioacchino Del Regno wrote:
> 
> > > +      regulator-allowed-modes:
> > > +        description: |
> > > +          Allowed Buck regulator operating modes allowed. Valid values below.
> 
> > > +        minItems: 1
> > > +        maxItems: 3
> > > +        items:
> > > +          enum: [ 0, 1, 2 ]
> 
> > This property has no default, and the property is not required. Is one
> > of these modes the default, or is there another mode beyond what's here
> > that is used if the property is absent? Or are all modes allowed with no
> > property?
> 
> The general approach the regulator API takes with everything is that if
> there is no explict configuration then it will simply not touch the
> hardware.  If nothing is configured then the hardware will be left in
> whatever state we found it in which could be anything as far as we know,
> it might vary depending on what was running before and what it was doing.

Okay, thanks for explaining Mark.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2025-10-26 22:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-24  8:32 [PATCH v10 0/9] Add support MT6316/6363/MT6373 PMICs regulators and MFD AngeloGioacchino Del Regno
2025-10-24  8:32 ` [PATCH v10 1/9] dt-bindings: regulator: Document MediaTek MT6316 PMIC Regulators AngeloGioacchino Del Regno
2025-10-24 10:10   ` Rob Herring (Arm)
2025-10-24 16:29   ` Conor Dooley
2025-10-24 18:24     ` Mark Brown
2025-10-26 22:21       ` Conor Dooley [this message]
2025-10-27 10:23     ` AngeloGioacchino Del Regno
2025-10-24  8:32 ` [PATCH v10 2/9] regulator: Add support for MediaTek MT6316 SPMI " AngeloGioacchino Del Regno
2025-10-24  8:32 ` [PATCH v10 3/9] dt-bindings: regulator: Document MediaTek MT6363 " AngeloGioacchino Del Regno
2025-10-24  8:32 ` [PATCH v10 4/9] regulator: Add support for MediaTek MT6363 SPMI " AngeloGioacchino Del Regno
2025-10-24  8:32 ` [PATCH v10 5/9] dt-bindings: regulator: Document MediaTek MT6373 " AngeloGioacchino Del Regno
2025-10-24  8:32 ` [PATCH v10 6/9] regulator: Add support for MediaTek MT6373 SPMI " AngeloGioacchino Del Regno
2025-10-24  8:32 ` [PATCH v10 7/9] dt-bindings: iio: adc: mt6359: Allow reg for SPMI PMICs AuxADC AngeloGioacchino Del Regno
2025-10-24  8:32 ` [PATCH v10 8/9] dt-bindings: mfd: Add binding for MediaTek MT6363 series SPMI PMIC AngeloGioacchino Del Regno
2025-10-24  8:32 ` [PATCH v10 9/9] mfd: Add support for MediaTek SPMI PMICs and MT6363/73 AngeloGioacchino Del Regno

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=20251026-despise-treadmill-12636f1a476f@spud \
    --to=conor@kernel.org \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=igor.belwon@mentallysanemainliners.org \
    --cc=kernel@collabora.com \
    --cc=krzk+dt@kernel.org \
    --cc=lee@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=robh@kernel.org \
    --cc=wenst@chromium.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