[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aQoNPvwUCE9PijJ6@finisterre.sirena.org.uk>
Date: Tue, 4 Nov 2025 14:27:10 +0000
From: Mark Brown <broonie@...nel.org>
To: André Draszik <andre.draszik@...aro.org>
Cc: Tudor Ambarus <tudor.ambarus@...aro.org>, Rob Herring <robh@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Krzysztof Kozlowski <krzk@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>, Lee Jones <lee@...nel.org>,
Linus Walleij <linus.walleij@...aro.org>,
Bartosz Golaszewski <brgl@...ev.pl>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Peter Griffin <peter.griffin@...aro.org>,
Will McVicker <willmcvicker@...gle.com>, kernel-team@...roid.com,
linux-kernel@...r.kernel.org, linux-samsung-soc@...r.kernel.org,
devicetree@...r.kernel.org, linux-gpio@...r.kernel.org
Subject: Re: [PATCH v3 10/20] regulator: add REGULATOR_LINEAR_VRANGE macro
On Mon, Nov 03, 2025 at 07:14:49PM +0000, André Draszik wrote:
> REGULATOR_LINEAR_VRANGE is similar to REGULATOR_LINEAR_RANGE, but
> allows a more natural declaration of a voltage range for a regulator,
> in that it expects the minimum and maximum values as voltages rather
> than as selectors.
> Using voltages arguably makes this macro easier to use by drivers and
> code using it can become easier to read compared to
> REGULATOR_LINEAR_RANGE.
It does introduce an additional layer of indirection into the validation
that the configuration is correct, the reason we use selectors is that
they should map directly onto the register in the datasheet.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists