From: Lorenzo Bianconi <lorenzo@kernel.org>
To: jic23@kernel.org
Cc: lorenzo.bianconi@redhat.com, linux-iio@vger.kernel.org,
martin.kepplinger@puri.sm, rjones@gateworks.com
Subject: [PATCH 0/3] st_lsm6dsx: do not access active-low/open-drain if not supported
Date: Sun, 22 Sep 2019 11:18:50 +0200 [thread overview]
Message-ID: <cover.1569143551.git.lorenzo@kernel.org> (raw)
Move active low and open drain register definitions in hw_settings
register map in order to avoid to access them if the sensor does not
support them.
Group irq related definition in irq_config structure in
st_lsm6dsx_settings.
@Jonathan: I post this series now since in this way Bobby can test it and maybe
you want to apply it on top of togreg branch. If you prefer to add it on
testing branch I can rebase it ontop of Sean's series.
Lorenzo Bianconi (3):
iio: imu: st_lsm6dsx: move irq related definitions in irq_config
iio: imu: st_lsm6dsx: do not access active-low/open-drain regs if not
supported
iio: imu: st_lsm6dsx: add sanity check for read_fifo pointer
drivers/iio/imu/st_lsm6dsx/st_lsm6dsx.h | 17 +-
.../iio/imu/st_lsm6dsx/st_lsm6dsx_buffer.c | 35 ++-
drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c | 243 ++++++++++++------
3 files changed, 203 insertions(+), 92 deletions(-)
--
2.21.0
next reply other threads:[~2019-09-22 9:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-22 9:18 Lorenzo Bianconi [this message]
2019-09-22 9:18 ` [PATCH 1/3] iio: imu: st_lsm6dsx: move irq related definitions in irq_config Lorenzo Bianconi
2019-09-24 13:51 ` Martin Kepplinger
2019-09-22 9:18 ` [PATCH 2/3] iio: imu: st_lsm6dsx: do not access active-low/open-drain regs if not supported Lorenzo Bianconi
2019-09-24 13:52 ` Martin Kepplinger
2019-09-24 14:07 ` Lorenzo Bianconi
2019-09-22 9:18 ` [PATCH 3/3] iio: imu: st_lsm6dsx: add sanity check for read_fifo pointer Lorenzo Bianconi
2019-09-24 13:52 ` Martin Kepplinger
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=cover.1569143551.git.lorenzo@kernel.org \
--to=lorenzo@kernel.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=martin.kepplinger@puri.sm \
--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.