From: Jonathan Cameron <jic23@kernel.org>
To: Alison Schofield <amsfield22@gmail.com>
Cc: knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: pressure: mpl3115: claim direct mode during raw reads
Date: Sat, 15 Oct 2016 15:59:58 +0100 [thread overview]
Message-ID: <915d3140-1b52-aaf8-13ce-1d2d264f04cf@kernel.org> (raw)
In-Reply-To: <20161011193306.GA8724@d830.WORKGROUP>
On 11/10/16 20:33, Alison Schofield wrote:
> Driver was checking for direct mode but not locking it. Use
> claim/release helper functions to guarantee the device stays
> in direct mode during raw reads.
>
> Signed-off-by: Alison Schofield <amsfield22@gmail.com>
breaks again also the goto goes to an 'unsual location'.
You don't even need the gotos if you put that unwind code
in the standard spot and use break whenever there is an error
to drop out of the switch statement.
I've fixed up and applied, please take a look.
Applied to the togreg branch of iio.git and pushed out
as testing for the autobuilders to play with it.
Thanks,
Jonathan
> ---
> drivers/iio/pressure/mpl3115.c | 23 ++++++++++++++---------
> 1 file changed, 14 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/iio/pressure/mpl3115.c b/drivers/iio/pressure/mpl3115.c
> index 6392d7b..fb36f7d 100644
> --- a/drivers/iio/pressure/mpl3115.c
> +++ b/drivers/iio/pressure/mpl3115.c
> @@ -82,8 +82,9 @@ static int mpl3115_read_raw(struct iio_dev *indio_dev,
>
> switch (mask) {
> case IIO_CHAN_INFO_RAW:
> - if (iio_buffer_enabled(indio_dev))
> - return -EBUSY;
> + ret = iio_device_claim_direct_mode(indio_dev);
> + if (ret)
> + return ret;
>
> switch (chan->type) {
> case IIO_PRESSURE: /* in 0.25 pascal / LSB */
> @@ -91,31 +92,35 @@ static int mpl3115_read_raw(struct iio_dev *indio_dev,
> ret = mpl3115_request(data);
> if (ret < 0) {
> mutex_unlock(&data->lock);
> - return ret;
> + goto release;
> }
> ret = i2c_smbus_read_i2c_block_data(data->client,
> MPL3115_OUT_PRESS, 3, (u8 *) &tmp);
> mutex_unlock(&data->lock);
> if (ret < 0)
> - return ret;
> + goto release;
> *val = be32_to_cpu(tmp) >> 12;
> - return IIO_VAL_INT;
> + ret = IIO_VAL_INT;
> case IIO_TEMP: /* in 0.0625 celsius / LSB */
> mutex_lock(&data->lock);
> ret = mpl3115_request(data);
> if (ret < 0) {
> mutex_unlock(&data->lock);
> - return ret;
> + goto release;
> }
> ret = i2c_smbus_read_i2c_block_data(data->client,
> MPL3115_OUT_TEMP, 2, (u8 *) &tmp);
> mutex_unlock(&data->lock);
> if (ret < 0)
> - return ret;
> + goto release;
> *val = sign_extend32(be32_to_cpu(tmp) >> 20, 11);
> - return IIO_VAL_INT;
> + ret = IIO_VAL_INT;
> default:
> - return -EINVAL;
> + ret = -EINVAL;
> +
> +release:
> + iio_device_release_direct_mode(indio_dev);
> + return ret;
> }
> case IIO_CHAN_INFO_SCALE:
> switch (chan->type) {
>
prev parent reply other threads:[~2016-10-15 15:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 19:33 [PATCH] iio: pressure: mpl3115: claim direct mode during raw reads Alison Schofield
2016-10-15 14:59 ` Jonathan Cameron [this message]
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=915d3140-1b52-aaf8-13ce-1d2d264f04cf@kernel.org \
--to=jic23@kernel.org \
--cc=amsfield22@gmail.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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