From: Jonathan Cameron <jic23@kernel.org>
To: Akinobu Mita <akinobu.mita@gmail.com>
Cc: linux-iio@vger.kernel.org, daniel.baluta@gmail.com
Subject: Re: [PATCH 7/8] iio: adc: ti-ads1015: use iio_device_claim_direct_mode()
Date: Sat, 15 Jul 2017 13:30:24 +0100 [thread overview]
Message-ID: <20170715133024.62312d43@kernel.org> (raw)
In-Reply-To: <1499877124-21658-8-git-send-email-akinobu.mita@gmail.com>
On Thu, 13 Jul 2017 01:32:03 +0900
Akinobu Mita <akinobu.mita@gmail.com> wrote:
> While the iio buffer for the ti-ads1015 driver is enabled, reading the
> raw ADC channel data is restricted. We usually use the
> iio_device_claim_direct_mode()/iio_device_release_direct_mode() pair for
> that.
>
> This change consequently reverses the locking order for the driver's
> private lock and indio_dev->mlock which acquired by
> iio_device_claim_direct_mode() internally. But it's safe because there is
> no other dependency between these locks.
>
> Cc: Daniel Baluta <daniel.baluta@intel.com>
> Cc: Jonathan Cameron <jic23@kernel.org>
> Signed-off-by: Akinobu Mita <akinobu.mita@gmail.com>
Sensible cleanup. Will pick up when rest are sorted.
Jonathan
> ---
> drivers/iio/adc/ti-ads1015.c | 15 +++++++--------
> 1 file changed, 7 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/iio/adc/ti-ads1015.c b/drivers/iio/adc/ti-ads1015.c
> index 821e649..dfeb3af 100644
> --- a/drivers/iio/adc/ti-ads1015.c
> +++ b/drivers/iio/adc/ti-ads1015.c
> @@ -340,34 +340,34 @@ static int ads1015_read_raw(struct iio_dev *indio_dev,
> int ret, idx;
> struct ads1015_data *data = iio_priv(indio_dev);
>
> - mutex_lock(&indio_dev->mlock);
> mutex_lock(&data->lock);
> switch (mask) {
> case IIO_CHAN_INFO_RAW: {
> int shift = chan->scan_type.shift;
>
> - if (iio_buffer_enabled(indio_dev)) {
> - ret = -EBUSY;
> + ret = iio_device_claim_direct_mode(indio_dev);
> + if (ret)
> break;
> - }
>
> ret = ads1015_set_power_state(data, true);
> if (ret < 0)
> - break;
> + goto release_direct;
>
> ret = ads1015_get_adc_result(data, chan->address, val);
> if (ret < 0) {
> ads1015_set_power_state(data, false);
> - break;
> + goto release_direct;
> }
>
> *val = sign_extend32(*val >> shift, 15 - shift);
>
> ret = ads1015_set_power_state(data, false);
> if (ret < 0)
> - break;
> + goto release_direct;
>
> ret = IIO_VAL_INT;
> +release_direct:
> + iio_device_release_direct_mode(indio_dev);
> break;
> }
> case IIO_CHAN_INFO_SCALE:
> @@ -386,7 +386,6 @@ static int ads1015_read_raw(struct iio_dev *indio_dev,
> break;
> }
> mutex_unlock(&data->lock);
> - mutex_unlock(&indio_dev->mlock);
>
> return ret;
> }
next prev parent reply other threads:[~2017-07-15 12:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 16:31 [PATCH 0/8] iio: adc: ti-ads1015: fixes, cleanups, and threshold event support Akinobu Mita
2017-07-12 16:31 ` [PATCH 1/8] iio: adc: ti-ads1015: fix incorrect data rate setting update Akinobu Mita
2017-07-15 12:16 ` Jonathan Cameron
2017-07-12 16:31 ` [PATCH 2/8] iio: adc: ti-ads1015: remove unnecessary config register update Akinobu Mita
2017-07-15 12:19 ` Jonathan Cameron
2017-07-12 16:31 ` [PATCH 3/8] iio: adc: ti-ads1015: fix scale information for ADS1115 Akinobu Mita
2017-07-15 12:21 ` Jonathan Cameron
2017-07-12 16:32 ` [PATCH 4/8] iio: adc: ti-ads1015: enable conversion when CONFIG_PM is not set Akinobu Mita
2017-07-15 12:24 ` Jonathan Cameron
2017-07-12 16:32 ` [PATCH 5/8] iio: adc: ti-ads1015: avoid getting stale result after runtime resume Akinobu Mita
2017-07-15 12:25 ` Jonathan Cameron
2017-07-12 16:32 ` [PATCH 6/8] iio: adc: ti-ads1015: use devm_iio_triggered_buffer_setup Akinobu Mita
2017-07-15 12:28 ` Jonathan Cameron
2017-07-16 16:02 ` Akinobu Mita
2017-07-17 11:52 ` Jonathan Cameron
2017-07-12 16:32 ` [PATCH 7/8] iio: adc: ti-ads1015: use iio_device_claim_direct_mode() Akinobu Mita
2017-07-15 12:30 ` Jonathan Cameron [this message]
2017-07-12 16:32 ` [PATCH 8/8] iio: adc: ti-ads1015: add threshold event support Akinobu Mita
2017-07-15 12:45 ` Jonathan Cameron
2017-07-17 16:45 ` Akinobu Mita
2017-07-17 20:35 ` 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=20170715133024.62312d43@kernel.org \
--to=jic23@kernel.org \
--cc=akinobu.mita@gmail.com \
--cc=daniel.baluta@gmail.com \
--cc=linux-iio@vger.kernel.org \
/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).