From: Sean Nyekjaer <sean@geanix.com>
To: Lorenzo Bianconi <lorenzo@kernel.org>
Cc: linux-iio@vger.kernel.org, jic23@kernel.org,
lorenzo.bianconi83@gmail.com, denis.ciocca@st.com,
mario.tesi@st.com, armando.visconti@st.com, martin@geanix.com
Subject: Re: [PATCH v6 6/6] iio: imu: st_lsm6dsx: prohibit the use of events and buffered reads simultaneously
Date: Mon, 9 Sep 2019 13:59:08 +0200 [thread overview]
Message-ID: <400fa605-ce9d-bd57-b757-d8875ec1d66b@geanix.com> (raw)
In-Reply-To: <20190909115535.GD2990@localhost.localdomain>
On 09/09/2019 13.55, Lorenzo Bianconi wrote:
>> When events and buffered reads is enabled simultaneously, and the first
>> event accours the interrupt pin stays high.
>>
>> This can be reverted when we find a solution to allow events and
>> buffered reads simultaneously.
>>
>> Signed-off-by: Sean Nyekjaer <sean@geanix.com>
>> ---
>> Changes since v4:
>> * Use fifo configuration mutex to prevent a race in hw->enable_event check.
>>
>> Changes since v5:
>> * Updated do not return without unlocking mutexes
>> * Lock mutex before unlock
>> * Runtime tested ;-)
>>
>
> [...]
>
>> --- a/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c
>> +++ b/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c
>> @@ -1340,8 +1340,12 @@ static int st_lsm6dsx_write_event_config(struct iio_dev *iio_dev,
>> if (type != IIO_EV_TYPE_THRESH)
>> return -EINVAL;
>>
>> - if (hw->fifo_mode != ST_LSM6DSX_FIFO_BYPASS)
>> - return -EBUSY;
>> + mutex_lock(&hw->conf_lock);
>> +
>> + if (hw->fifo_mode != ST_LSM6DSX_FIFO_BYPASS) {
>> + err = -EBUSY;
>> + goto out;
>> + }
>
> This patch is still broken!!! Returning in case of error you need to relase the
> lock.
>
Hmm,
please read below this:
- return 0;
+out:
+ mutex_unlock(&hw->conf_lock);
+
+ return err;
>>
>> /* do not enable events if they are already enabled */
>> if (state && hw->enable_event)
>> @@ -1357,7 +1361,10 @@ static int st_lsm6dsx_write_event_config(struct iio_dev *iio_dev,
>>
>> hw->enable_event = state;
>>
>> - return 0;
>> +out:
>> + mutex_unlock(&hw->conf_lock);
>> +
>> + return err;
>> }
>>
>> int st_lsm6dsx_set_watermark(struct iio_dev *iio_dev, unsigned int val)
>> --
>> 2.23.0
>>
next prev parent reply other threads:[~2019-09-09 11:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 11:28 [PATCH v6 1/6] iio: imu: st_lsm6dsx: move interrupt thread to core Sean Nyekjaer
2019-09-09 11:28 ` [PATCH v6 2/6] iio: imu: st_lsm6dsx: add motion events Sean Nyekjaer
2019-09-09 11:28 ` [PATCH v6 3/6] iio: imu: st_lsm6dsx: add wakeup-source option Sean Nyekjaer
2019-09-09 11:28 ` [PATCH v6 4/6] iio: imu: st_lsm6dsx: always enter interrupt thread Sean Nyekjaer
2019-09-09 11:28 ` [PATCH v6 5/6] iio: imu: st_lsm6dsx: add motion report function and call from interrupt Sean Nyekjaer
2019-09-09 11:51 ` Sean Nyekjaer
2019-09-15 12:20 ` Jonathan Cameron
2019-09-15 12:24 ` Sean Nyekjaer
2019-09-15 13:06 ` Jonathan Cameron
2019-09-09 12:05 ` Lorenzo Bianconi
2019-09-09 12:41 ` Sean Nyekjaer
2019-09-10 7:12 ` Lorenzo Bianconi
2019-09-10 7:17 ` Sean Nyekjaer
2019-09-10 7:26 ` Lorenzo Bianconi
2019-09-10 12:27 ` Lorenzo Bianconi
2019-09-11 12:41 ` Sean Nyekjaer
2019-09-11 12:59 ` Lorenzo Bianconi
2019-09-09 11:28 ` [PATCH v6 6/6] iio: imu: st_lsm6dsx: prohibit the use of events and buffered reads simultaneously Sean Nyekjaer
2019-09-09 11:55 ` Lorenzo Bianconi
2019-09-09 11:59 ` Sean Nyekjaer [this message]
2019-09-09 12:01 ` Sean Nyekjaer
2019-09-09 12:45 ` [PATCH v6.1 " Sean Nyekjaer
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=400fa605-ce9d-bd57-b757-d8875ec1d66b@geanix.com \
--to=sean@geanix.com \
--cc=armando.visconti@st.com \
--cc=denis.ciocca@st.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=lorenzo.bianconi83@gmail.com \
--cc=lorenzo@kernel.org \
--cc=mario.tesi@st.com \
--cc=martin@geanix.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;
as well as URLs for NNTP newsgroup(s).