[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240504122504.0389b872@jic23-huawei>
Date: Sat, 4 May 2024 12:25:04 +0100
From: Jonathan Cameron <jic23@...nel.org>
To: David Lechner <dlechner@...libre.com>
Cc: Liam Girdwood <lgirdwood@...il.com>, Mark Brown <broonie@...nel.org>,
Jean Delvare <jdelvare@...e.com>, Guenter Roeck <linux@...ck-us.net>,
Dmitry Torokhov <dmitry.torokhov@...il.com>, Jonathan Corbet
<corbet@....net>, Support Opensource <support.opensource@...semi.com>,
Cosmin Tanislav <cosmin.tanislav@...log.com>, Lars-Peter Clausen
<lars@...afoo.de>, Michael Hennerich <Michael.Hennerich@...log.com>,
Antoniu Miclaus <antoniu.miclaus@...log.com>, Greg Kroah-Hartman
<gregkh@...uxfoundation.org>, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-hwmon@...r.kernel.org,
linux-iio@...r.kernel.org, linux-staging@...ts.linux.dev,
linux-input@...r.kernel.org
Subject: Re: [PATCH v2 4/7] iio: addac: ad74115: Use
devm_regulator_get_enable_read_voltage()
On Mon, 29 Apr 2024 18:40:12 -0500
David Lechner <dlechner@...libre.com> wrote:
> We can reduce boilerplate code by using
> devm_regulator_get_enable_read_voltage().
>
> To maintain backwards compatibility in the case a DT does not provide
> an avdd-supply, we fall back to calling devm_regulator_get_enable()
> so that there is no change in user-facing behavior (e.g. dummy regulator
> will still be in sysfs).
>
> Also add an informative error message when we failed to get the voltage
> and knowing the voltage is required while we are touching this.
>
> Signed-off-by: David Lechner <dlechner@...libre.com>
A somewhat fiddly case. I think you've done it the best way possible though.
Acked-by: Jonathan Cameron <Jonathan.Cameron@...wei.com>
Powered by blists - more mailing lists