From: Jonathan Cameron <jic23@kernel.org>
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/4] iio: vcnl4000: Factorize data reading and writing.
Date: Sun, 26 Apr 2020 09:58:31 +0100 [thread overview]
Message-ID: <20200426095831.1472fbc9@archlinux> (raw)
In-Reply-To: <20200422130856.1722-2-m.othacehe@gmail.com>
On Wed, 22 Apr 2020 15:08:53 +0200
Mathieu Othacehe <m.othacehe@gmail.com> wrote:
> Factorize data reading in vcnl4000_measure into a vcnl4000_read_data
> function. Also add a vcnl4000_write_data function.
>
> Signed-off-by: Mathieu Othacehe <m.othacehe@gmail.com>
> ---
> drivers/iio/light/vcnl4000.c | 29 +++++++++++++++++++++++++----
> 1 file changed, 25 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/iio/light/vcnl4000.c b/drivers/iio/light/vcnl4000.c
> index 58e97462e803..695a81e95d8d 100644
> --- a/drivers/iio/light/vcnl4000.c
> +++ b/drivers/iio/light/vcnl4000.c
> @@ -215,11 +215,34 @@ static int vcnl4200_init(struct vcnl4000_data *data)
> return 0;
> };
>
> +static int vcnl4000_read_data(struct vcnl4000_data *data, u8 data_reg, int *val)
> +{
> + s32 ret;
> +
> + ret = i2c_smbus_read_word_data(data->client, data_reg);
> + if (ret < 0)
> + return ret;
> +
> + *val = be16_to_cpu(ret);
> + return 0;
> +}
> +
> +static int vcnl4000_write_data(struct vcnl4000_data *data, u8 data_reg, int val)
> +{
> + __be16 be_val;
> +
> + if (val > U16_MAX)
> + return -ERANGE;
> +
> + be_val = cpu_to_be16(val);
> + return i2c_smbus_write_word_data(data->client, data_reg, be_val);
> +}
> +
> +
Nitpick: One line is plenty. I can tidy this up whilst applying if
we don't go to v6 for other reasons.
Otherwise this looks fine.
Jonathan
> static int vcnl4000_measure(struct vcnl4000_data *data, u8 req_mask,
> u8 rdy_mask, u8 data_reg, int *val)
> {
> int tries = 20;
> - __be16 buf;
> int ret;
>
> mutex_lock(&data->vcnl4000_lock);
> @@ -246,13 +269,11 @@ static int vcnl4000_measure(struct vcnl4000_data *data, u8 req_mask,
> goto fail;
> }
>
> - ret = i2c_smbus_read_i2c_block_data(data->client,
> - data_reg, sizeof(buf), (u8 *) &buf);
> + ret = vcnl4000_read_data(data, data_reg, val);
> if (ret < 0)
> goto fail;
>
> mutex_unlock(&data->vcnl4000_lock);
> - *val = be16_to_cpu(buf);
>
> return 0;
>
next prev parent reply other threads:[~2020-04-26 8:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 13:08 [PATCH v5 0/4] iio: vcnl: Add interrupts support for VCNL4010/20 Mathieu Othacehe
2020-04-22 13:08 ` [PATCH v5 1/4] iio: vcnl4000: Factorize data reading and writing Mathieu Othacehe
2020-04-26 8:58 ` Jonathan Cameron [this message]
2020-04-26 9:24 ` Jonathan Cameron
2020-04-22 13:08 ` [PATCH v5 2/4] iio: vcnl4000: Add event support for VCNL4010/20 Mathieu Othacehe
2020-04-26 9:17 ` Jonathan Cameron
2020-04-22 13:08 ` [PATCH v5 3/4] iio: vcnl4000: Add sampling frequency " Mathieu Othacehe
2020-04-26 9:18 ` Jonathan Cameron
2020-04-22 13:08 ` [PATCH v5 4/4] iio: vcnl4000: Add buffer " Mathieu Othacehe
2020-04-26 9:18 ` 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=20200426095831.1472fbc9@archlinux \
--to=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.othacehe@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).