[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240615130858.22043725@jic23-huawei>
Date: Sat, 15 Jun 2024 13:08:58 +0100
From: Jonathan Cameron <jic23@...nel.org>
To: David Lechner <dlechner@...libre.com>
Cc: Marcelo Schmitt <marcelo.schmitt1@...il.com>, Nuno Sá
<nuno.sa@...log.com>, Michael Hennerich <Michael.Hennerich@...log.com>,
Mark Brown <broonie@...nel.org>, Liam Girdwood <lgirdwood@...il.com>,
linux-iio@...r.kernel.org, linux-kernel@...r.kernel.org, Alisa-Dariana
Roman <alisadariana@...il.com>
Subject: Re: [PATCH v2 1/5] iio: adc: ad7192: use
devm_regulator_get_enable_read_voltage
On Wed, 12 Jun 2024 16:03:05 -0500
David Lechner <dlechner@...libre.com> wrote:
> This makes use of the new devm_regulator_get_enable_read_voltage()
> function to reduce boilerplate code.
>
> Error messages have changed slightly since there are now fewer places
> where we print an error. The rest of the logic of selecting which
> supply to use as the reference voltage remains the same.
>
> Also 1000 is replaced by MILLI in a few places for consistency.
>
> Signed-off-by: David Lechner <dlechner@...libre.com>
Complicated bit of code, but seems correct.
However, it crossed with Alisa-Dariana switching adding a
struct device *dev = &spi->dev to probe() that I picked up earlier
today.
I could unwind that but given Alisa-Dariana has a number of
other patches on this driver in flight, I'd like the two of you
to work out the best resolution between you. Maybe easiest option
is that Alisa-Dariana sends this a first patch of the next
series I should pick up.
Thanks,
Jonathan
Powered by blists - more mailing lists