From: Jonathan Cameron <jic23@kernel.org>
To: carlos.song@nxp.com
Cc: lars@metafoo.de, rjones@gateworks.com,
Jonathan.Cameron@huawei.com, haibo.chen@nxp.com,
linux-imx@nxp.com, linux-iio@vger.kernel.org
Subject: Re: [PATCH v3 1/5] iio: imu: fxos8700: fix incorrect ODR mode readback
Date: Fri, 23 Dec 2022 16:58:05 +0000 [thread overview]
Message-ID: <20221223165805.1bf518bc@jic23-huawei> (raw)
In-Reply-To: <20221223165529.08c491cb@jic23-huawei>
On Fri, 23 Dec 2022 16:55:29 +0000
Jonathan Cameron <jic23@kernel.org> wrote:
> On Wed, 14 Dec 2022 11:14:59 +0800
> carlos.song@nxp.com wrote:
>
> > From: Carlos Song <carlos.song@nxp.com>
> >
> > The absence of a correct offset leads an incorrect ODR mode
> > readback after use a hexadecimal number to mark the value from
> > FXOS8700_CTRL_REG1.
> >
> > Get ODR mode by field mask and FIELD_GET clearly and conveniently.
> >
> > Fixes: 84e5ddd5c46e ("iio: imu: Add support for the FXOS8700 IMU")
> > Signed-off-by: Carlos Song <carlos.song@nxp.com>
> >
> You need a
> ---
>
> above the change log to avoid git picking it up when I apply the patch.
> I've fixed that up whilst applying.
>
> Applied to the fixes-togreg branch of iio.git and marked for stable.
Dropped again because this makes no sense wrt to split of what is
going on in patch 2.
>
> > Changes for V3:
> > - Rework commit log
> >
> > diff --git a/drivers/iio/imu/fxos8700_core.c b/drivers/iio/imu/fxos8700_core.c
> > index 773f62203bf0..83ab7d0f79b3 100644
> > --- a/drivers/iio/imu/fxos8700_core.c
> > +++ b/drivers/iio/imu/fxos8700_core.c
> > @@ -10,6 +10,7 @@
> > #include <linux/regmap.h>
> > #include <linux/acpi.h>
> > #include <linux/bitops.h>
> > +#include <linux/bitfield.h>
> >
> > #include <linux/iio/iio.h>
> > #include <linux/iio/sysfs.h>
> > @@ -147,6 +148,7 @@
> > #define FXOS8700_CTRL_ODR_MSK 0x38
> > #define FXOS8700_CTRL_ODR_MAX 0x00
> > #define FXOS8700_CTRL_ODR_MIN GENMASK(4, 3)
> > +#define FXOS8700_CTRL_ODR_GENMSK GENMASK(5, 3)
> >
> > /* Bit definitions for FXOS8700_M_CTRL_REG1 */
> > #define FXOS8700_HMS_MASK GENMASK(1, 0)
> > @@ -524,7 +526,7 @@ static int fxos8700_get_odr(struct fxos8700_data *data, enum fxos8700_sensor t,
> > if (ret)
> > return ret;
> >
> > - val &= FXOS8700_CTRL_ODR_MSK;
> > + val = FIELD_GET(FXOS8700_CTRL_ODR_GENMSK, val);
> >
> > for (i = 0; i < odr_num; i++)
> > if (val == fxos8700_odr[i].bits)
>
next prev parent reply other threads:[~2022-12-23 16:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 3:14 [PATCH v3 0/5] iio: imu: fxos8700: fix bugs about ODR and changes for a good readability carlos.song
2022-12-14 3:14 ` [PATCH v3 1/5] iio: imu: fxos8700: fix incorrect ODR mode readback carlos.song
2022-12-23 16:55 ` Jonathan Cameron
2022-12-23 16:58 ` Jonathan Cameron [this message]
2022-12-14 3:15 ` [PATCH v3 2/5] iio: imu: fxos8700: improve readability by field mask and regmap_write carlos.song
2022-12-23 16:59 ` Jonathan Cameron
2022-12-14 3:15 ` [PATCH v3 3/5] iio: imu: fxos8700: fix failed initialization ODR mode assignment carlos.song
2022-12-14 3:15 ` [PATCH v3 4/5] iio: imu: fxos8700: remove definition FXOS8700_CTRL_ODR_MIN carlos.song
2022-12-14 3:15 ` [PATCH v3 5/5] iio: imu: fxos8700: fix MAGN sensor scale and unit carlos.song
2022-12-23 17:01 ` 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=20221223165805.1bf518bc@jic23-huawei \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=carlos.song@nxp.com \
--cc=haibo.chen@nxp.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=rjones@gateworks.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox