From: Jonathan Cameron <jic23@kernel.org>
To: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH v2] iio: imu: st_lsm6dsx: do not use a fixed read len in read_oneshot
Date: Sun, 25 Nov 2018 14:06:59 +0000 [thread overview]
Message-ID: <20181125140659.39a542f7@archlinux> (raw)
In-Reply-To: <2eefd3a4e60701fef40f31eacd2e79c1cffe6311.1542477399.git.lorenzo.bianconi@redhat.com>
On Sat, 17 Nov 2018 19:04:27 +0100
Lorenzo Bianconi <lorenzo.bianconi@redhat.com> wrote:
> Generalize st_lsm6dsx_shub_read_oneshot in order to not use a fixed
> read length and take into account iio channel realbits for single
> read operations
>
> Signed-off-by: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Applied to the togreg branch of iio.git and pushed out as testing for
the autobuilders to play with it.
Thanks,
Jonathan
> ---
> Changes since v1:
> - allocate data buffer on the stack instead of using kmalloc
> - stop the sensor even if the read operation fails
> ---
> drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_shub.c | 14 ++++++++------
> 1 file changed, 8 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_shub.c b/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_shub.c
> index ee59b0cac84f..8e47dccdd40f 100644
> --- a/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_shub.c
> +++ b/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_shub.c
> @@ -432,8 +432,8 @@ st_lsm6dsx_shub_read_oneshot(struct st_lsm6dsx_sensor *sensor,
> struct iio_chan_spec const *ch,
> int *val)
> {
> - int err, delay, len = ch->scan_type.realbits >> 3;
> - __le16 data;
> + int err, delay, len;
> + u8 data[4];
>
> err = st_lsm6dsx_shub_set_enable(sensor, true);
> if (err < 0)
> @@ -442,15 +442,17 @@ st_lsm6dsx_shub_read_oneshot(struct st_lsm6dsx_sensor *sensor,
> delay = 1000000 / sensor->odr;
> usleep_range(delay, 2 * delay);
>
> - err = st_lsm6dsx_shub_read(sensor, ch->address, (u8 *)&data, len);
> - if (err < 0)
> - return err;
> + len = min_t(int, sizeof(data), ch->scan_type.realbits >> 3);
> + err = st_lsm6dsx_shub_read(sensor, ch->address, data, len);
>
> st_lsm6dsx_shub_set_enable(sensor, false);
>
> + if (err < 0)
> + return err;
> +
> switch (len) {
> case 2:
> - *val = (s16)le16_to_cpu(data);
> + *val = (s16)le16_to_cpu(*((__le16 *)data));
> break;
> default:
> return -EINVAL;
prev parent reply other threads:[~2018-11-26 0:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1542477399.git.lorenzo.bianconi@redhat.com>
2018-11-17 18:04 ` [PATCH v2] iio: imu: st_lsm6dsx: do not use a fixed read len in read_oneshot Lorenzo Bianconi
2018-11-25 14:06 ` Jonathan Cameron [this message]
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=20181125140659.39a542f7@archlinux \
--to=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
/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.