From: carlos.song@nxp.com
To: jic23@kernel.org, lars@metafoo.de
Cc: rjones@gateworks.com, Jonathan.Cameron@huawei.com,
haibo.chen@nxp.com, carlos.song@nxp.com, linux-imx@nxp.com,
linux-iio@vger.kernel.org
Subject: [PATCH v5 0/4] iio: imu: fxos8700: fix bugs about ODR and changes for a good readability
Date: Wed, 18 Jan 2023 15:42:23 +0800 [thread overview]
Message-ID: <20230118074227.1665098-1-carlos.song@nxp.com> (raw)
From: Carlos Song <carlos.song@nxp.com>
Hi, Jonathan. Thank you for the suggestion. In patch 1, I use
regmap_write to modify the value of the register. And in patch 2,
I use regmap_update_bits instead of regmap_get and regmap_write
for a good readability. Other patches have not been changed.
Carlos Song (4):
iio: imu: fxos8700: fix incorrect ODR mode readback
iio: imu: fxos8700: fix failed initialization ODR mode assignment
iio: imu: fxos8700: remove definition FXOS8700_CTRL_ODR_MIN
iio: imu: fxos8700: fix MAGN sensor scale and unit
drivers/iio/imu/fxos8700_core.c | 25 +++++++++++++------------
1 file changed, 13 insertions(+), 12 deletions(-)
--
2.34.1
next reply other threads:[~2023-01-18 8:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 7:42 carlos.song [this message]
2023-01-18 7:42 ` [PATCH v5 1/4] iio: imu: fxos8700: fix incorrect ODR mode readback carlos.song
2023-01-18 7:42 ` [PATCH v5 2/4] iio: imu: fxos8700: fix failed initialization ODR mode assignment carlos.song
2023-01-18 7:42 ` [PATCH v5 3/4] iio: imu: fxos8700: remove definition FXOS8700_CTRL_ODR_MIN carlos.song
2023-01-18 7:42 ` [PATCH v5 4/4] iio: imu: fxos8700: fix MAGN sensor scale and unit carlos.song
2023-01-21 18:15 ` [PATCH v5 0/4] iio: imu: fxos8700: fix bugs about ODR and changes for a good readability 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=20230118074227.1665098-1-carlos.song@nxp.com \
--to=carlos.song@nxp.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=haibo.chen@nxp.com \
--cc=jic23@kernel.org \
--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 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.