linux-kernel - Re: [PATCH v10 1/9] dt-bindings: regulator: Document MediaTek MT6316 PMIC Regulators

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20251026-despise-treadmill-12636f1a476f@spud>
Date: Sun, 26 Oct 2025 22:21:54 +0000
From: Conor Dooley <conor@...nel.org>
To: Mark Brown <broonie@...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 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.

Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)