[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aPvETBr5aebElQUS@finisterre.sirena.org.uk>
Date: Fri, 24 Oct 2025 19:24:12 +0100
From: Mark Brown <broonie@...nel.org>
To: Conor Dooley <conor@...nel.org>
Cc: AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>,
linux-mediatek@...ts.infradead.org, lee@...nel.org, robh@...nel.org,
krzk+dt@...nel.org, conor+dt@...nel.org, matthias.bgg@...il.com,
lgirdwood@...il.com, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
kernel@...labora.com, wenst@...omium.org,
igor.belwon@...tallysanemainliners.org
Subject: Re: [PATCH v10 1/9] dt-bindings: regulator: Document MediaTek MT6316
PMIC Regulators
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.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists