From: Jonathan Cameron <jic23@kernel.org>
To: Hartmut Knaack <knaack.h@gmx.de>, linux-iio@vger.kernel.org
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald <pmeerw@pmeerw.net>,
Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Subject: Re: [PATCH 6/6] iio:dac:m62332: use dynamic scale
Date: Sun, 11 Oct 2015 15:46:00 +0100 [thread overview]
Message-ID: <561A7628.4020203@kernel.org> (raw)
In-Reply-To: <59133cb6c4c826e9fff4ab5504eb42c16d40fe70.1440459082.git.knaack.h@gmx.de>
On 28/08/15 22:59, Hartmut Knaack wrote:
> Some regulators can supply multiple voltages. To take changing voltages
> into account, the scale needs to be calculated on every read access.
>
> Signed-off-by: Hartmut Knaack <knaack.h@gmx.de>
This is a pretty common situation, but just because it is done
less than ideally in a lot of places, doesn't mean we shouldn't
fix this one!
Applied.
Jonathan
> ---
> drivers/iio/dac/m62332.c | 13 ++++++-------
> 1 file changed, 6 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/iio/dac/m62332.c b/drivers/iio/dac/m62332.c
> index fdb3e042c14d..76e8b044b979 100644
> --- a/drivers/iio/dac/m62332.c
> +++ b/drivers/iio/dac/m62332.c
> @@ -31,7 +31,6 @@
>
> struct m62332_data {
> struct i2c_client *client;
> - u16 vref_mv;
> struct regulator *vcc;
> struct mutex mutex;
> u8 raw[M62332_CHANNELS];
> @@ -89,11 +88,16 @@ static int m62332_read_raw(struct iio_dev *indio_dev,
> long mask)
> {
> struct m62332_data *data = iio_priv(indio_dev);
> + int ret;
>
> switch (mask) {
> case IIO_CHAN_INFO_SCALE:
> /* Corresponds to Vref / 2^(bits) */
> - *val = data->vref_mv;
> + ret = regulator_get_voltage(data->vcc);
> + if (ret < 0)
> + return ret;
> +
> + *val = ret / 1000; /* mV */
> *val2 = 8;
>
> return IIO_VAL_FRACTIONAL_LOG2;
> @@ -218,11 +222,6 @@ static int m62332_probe(struct i2c_client *client,
> indio_dev->modes = INDIO_DIRECT_MODE;
> indio_dev->info = &m62332_info;
>
> - ret = regulator_get_voltage(data->vcc);
> - if (ret < 0)
> - return ret;
> - data->vref_mv = ret / 1000; /* mV */
> -
> ret = iio_map_array_register(indio_dev, client->dev.platform_data);
> if (ret < 0)
> return ret;
>
next prev parent reply other threads:[~2015-10-11 14:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 21:59 [PATCH 0/6] fixes, cleanup and improvements for m62332 Hartmut Knaack
2015-08-28 21:59 ` [PATCH 1/6] iio:dac:m62332: share scale and offset Hartmut Knaack
2015-08-31 14:53 ` Jonathan Cameron
2015-09-12 10:11 ` Jonathan Cameron
2015-09-12 10:14 ` Jonathan Cameron
2015-09-27 15:56 ` Jonathan Cameron
2015-10-11 14:40 ` Jonathan Cameron
2015-08-28 21:59 ` [PATCH 2/6] iio:dac:m62332: shutdown on remove Hartmut Knaack
2015-08-31 12:56 ` Daniel Baluta
2015-08-31 19:26 ` Hartmut Knaack
2015-10-11 14:42 ` Jonathan Cameron
2015-08-28 21:59 ` [PATCH 3/6] iio:dac:m62332: use ARRAY_SIZE Hartmut Knaack
2015-08-31 12:58 ` Daniel Baluta
2015-10-11 14:43 ` Jonathan Cameron
2015-08-28 21:59 ` [PATCH 4/6] iio:dac:m62332: drop unrequired variable Hartmut Knaack
2015-08-31 19:46 ` Daniel Baluta
2015-10-11 14:44 ` Jonathan Cameron
2015-08-28 21:59 ` [PATCH 5/6] iio:dac:m62332: address some style issues Hartmut Knaack
2015-10-11 14:45 ` Jonathan Cameron
2015-08-28 21:59 ` [PATCH 6/6] iio:dac:m62332: use dynamic scale Hartmut Knaack
2015-10-11 14:46 ` Jonathan Cameron [this message]
2015-08-31 15:00 ` [PATCH 0/6] fixes, cleanup and improvements for m62332 Jonathan Cameron
2015-08-31 16:09 ` Dmitry Eremin-Solenikov
2015-09-12 10:13 ` Jonathan Cameron
2015-10-03 11:16 ` Jonathan Cameron
2015-10-11 14:38 ` Jonathan Cameron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=561A7628.4020203@kernel.org \
--to=jic23@kernel.org \
--cc=dbaryshkov@gmail.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.