From: Jonathan Cameron <jic23@kernel.org>
To: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/7] iio: imu: st_lsm6dsx: introduce locked read/write utility routines
Date: Sun, 4 Nov 2018 17:11:39 +0000 [thread overview]
Message-ID: <20181104171139.4ca2e848@archlinux> (raw)
In-Reply-To: <31af70f2f7b832b984b3f1bd122ce1c9cf98582b.1541341926.git.lorenzo.bianconi@redhat.com>
On Sun, 4 Nov 2018 15:39:00 +0100
Lorenzo Bianconi <lorenzo.bianconi@redhat.com> wrote:
> Add st_lsm6dsx_update_bits_locked, st_lsm6dsx_read_locked and
> st_lsm6dsx_write_locked utility routines in order to guarantee
> the bus access is atomic respect to reg page configuration.
> This is a preliminary patch to add i2c sensor hub support since
> i2c master registers are accessed through a reg page multiplexer
>
> Signed-off-by: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Just one case inline where this doesn't seem as straight forward a
change as this suggests..
Jonathan
> ---
...
> @@ -536,16 +541,11 @@ int st_lsm6dsx_read_tagged_fifo(struct st_lsm6dsx_hw *hw)
>
> int st_lsm6dsx_flush_fifo(struct st_lsm6dsx_hw *hw)
> {
> - int err;
> -
> mutex_lock(&hw->fifo_lock);
> -
> hw->settings->fifo_ops.read_fifo(hw);
> - err = st_lsm6dsx_set_fifo_mode(hw, ST_LSM6DSX_FIFO_BYPASS);
This one needs some explaining... You've dropped the set_fifo_mode
out of the fifo_lock. Is this because it was never needed or has
something changed? If it was never needed then I'd like to see it
moved out in a precursor patch where you explain why that is safe.
Basically I want this patch to be purely mechanical application of
a lock around places where we need the page to be held constant.
> -
> mutex_unlock(&hw->fifo_lock);
>
> - return err;
> + return st_lsm6dsx_set_fifo_mode(hw, ST_LSM6DSX_FIFO_BYPASS);
> }
>
> static int st_lsm6dsx_update_fifo(struct iio_dev *iio_dev, bool enable)
next prev parent reply other threads:[~2018-11-05 2:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-04 14:38 [PATCH 0/7] add i2c controller support to st_lsm6dsx driver Lorenzo Bianconi
2018-11-04 14:39 ` [PATCH 1/7] iio: imu: st_lsm6dsx: introduce locked read/write utility routines Lorenzo Bianconi
2018-11-04 17:11 ` Jonathan Cameron [this message]
2018-11-04 14:39 ` [PATCH 2/7] iio: imu: st_lsm6dsx: reboot memory content after reset Lorenzo Bianconi
2018-11-04 17:12 ` Jonathan Cameron
2018-11-04 17:30 ` Lorenzo Bianconi
2018-11-04 14:39 ` [PATCH 3/7] iio: imu: st_lsm6dsx: remove static from st_lsm6dsx_set_watermark Lorenzo Bianconi
2018-11-04 14:39 ` [PATCH 4/7] iio: imu: st_lsm6dsx: introduce ST_LSM6DSX_ID_EXT sensor ids Lorenzo Bianconi
2018-11-04 17:18 ` Jonathan Cameron
2018-11-04 17:47 ` Lorenzo Bianconi
2018-11-04 18:18 ` Jonathan Cameron
2018-11-04 14:39 ` [PATCH 5/7] iio: imu: st_lsm6dsx: add i2c embedded controller support Lorenzo Bianconi
2018-11-04 17:42 ` Jonathan Cameron
2018-11-04 18:00 ` Lorenzo Bianconi
2018-11-04 18:21 ` Jonathan Cameron
2018-11-04 18:29 ` Lorenzo Bianconi
2018-11-04 14:39 ` [PATCH 6/7] iio: imu: st_lsm6dsx: add hw FIFO support to i2c controller Lorenzo Bianconi
2018-11-04 17:54 ` Jonathan Cameron
2018-11-04 18:14 ` Lorenzo Bianconi
2018-11-04 18:31 ` Jonathan Cameron
2018-11-04 18:56 ` Lorenzo Bianconi
2018-11-04 14:39 ` [PATCH 7/7] dt-bindings: iio: imu: st_lsm6dsx: add support to i2c pullup resistors Lorenzo Bianconi
2018-11-04 18:12 ` [PATCH 0/7] add i2c controller support to st_lsm6dsx driver Jonathan Cameron
2018-11-04 18:27 ` Lorenzo Bianconi
2018-11-04 18:34 ` Jonathan Cameron
2018-11-04 19:07 ` Lorenzo Bianconi
2018-11-11 14:33 ` 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=20181104171139.4ca2e848@archlinux \
--to=jic23@kernel.org \
--cc=devicetree@vger.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.