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 5/5] iio: imu: fxos8700: fix MAGN sensor scale and unit
Date: Fri, 23 Dec 2022 17:01:16 +0000 [thread overview]
Message-ID: <20221223170116.5eed8649@jic23-huawei> (raw)
In-Reply-To: <20221214031503.3104251-6-carlos.song@nxp.com>
On Wed, 14 Dec 2022 11:15:03 +0800
carlos.song@nxp.com wrote:
> From: Carlos Song <carlos.song@nxp.com>
>
> +/-1200uT is a MAGN sensor full measurement range. Magnetometer scale
> is the magnetic sensitivity parameter. It is referenced as 0.1uT
> according to datasheet and magnetometer channel unit is Gauss in
> sysfs-bus-iio documentation. Gauss and uTesla unit conversion
> relationship as follows: 0.1uT = 0.001Gs.
>
> Set magnetometer scale and available magnetometer scale as fixed 0.001Gs.
>
> Fixes: 84e5ddd5c46e ("iio: imu: Add support for the FXOS8700 IMU")
> Signed-off-by: Carlos Song <carlos.song@nxp.com>
>
---
as for all the other patches.
3,4,5 look fine to me other than that. So I'll pick them up once
the patch 1/2 split is sorted out.
Jonathan
> Changes for V2:
> - Modify the magnetometer sensitivity unit to be consistent with the
> documentation as 0.001g
> - Rework commit log
> Changes for V3:
> - Modify the magnetometer sensitivity unit "g" to standard unit "Gs"
> - Check and confirm uscale value is correct. The readback of
> MAGN scale is 0.001 Gs
> - Rework commit log
>
> diff --git a/drivers/iio/imu/fxos8700_core.c b/drivers/iio/imu/fxos8700_core.c
> index 7b370bd643a1..8320a3b6f942 100644
> --- a/drivers/iio/imu/fxos8700_core.c
> +++ b/drivers/iio/imu/fxos8700_core.c
> @@ -351,7 +351,7 @@ static int fxos8700_set_scale(struct fxos8700_data *data,
> struct device *dev = regmap_get_device(data->regmap);
>
> if (t == FXOS8700_MAGN) {
> - dev_err(dev, "Magnetometer scale is locked at 1200uT\n");
> + dev_err(dev, "Magnetometer scale is locked at 0.001Gs\n");
> return -EINVAL;
> }
>
> @@ -396,7 +396,7 @@ static int fxos8700_get_scale(struct fxos8700_data *data,
> static const int scale_num = ARRAY_SIZE(fxos8700_accel_scale);
>
> if (t == FXOS8700_MAGN) {
> - *uscale = 1200; /* Magnetometer is locked at 1200uT */
> + *uscale = 1000; /* Magnetometer is locked at 0.001Gs */
> return 0;
> }
>
> @@ -587,7 +587,7 @@ static IIO_CONST_ATTR(in_accel_sampling_frequency_available,
> static IIO_CONST_ATTR(in_magn_sampling_frequency_available,
> "1.5625 6.25 12.5 50 100 200 400 800");
> static IIO_CONST_ATTR(in_accel_scale_available, "0.000244 0.000488 0.000976");
> -static IIO_CONST_ATTR(in_magn_scale_available, "0.000001200");
> +static IIO_CONST_ATTR(in_magn_scale_available, "0.001000");
>
> static struct attribute *fxos8700_attrs[] = {
> &iio_const_attr_in_accel_sampling_frequency_available.dev_attr.attr,
prev parent reply other threads:[~2022-12-23 16:48 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
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 [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=20221223170116.5eed8649@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