linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alison Schofield <amsfield22@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>
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: magnetometer: mag3110: claim direct mode during raw reads
Date: Mon, 15 Aug 2016 15:16:22 -0700	[thread overview]
Message-ID: <20160815221607.GA4567@d830.WORKGROUP> (raw)
In-Reply-To: <14defd5e-ef8c-047a-0512-e94835629201@kernel.org>

On Mon, Aug 15, 2016 at 05:04:24PM +0100, Jonathan Cameron wrote:
> On 01/08/16 16:48, 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>
> > Cc: Daniel Baluta <daniel.baluta@gmail.com>
> > ---
> >  drivers/iio/magnetometer/mag3110.c | 21 +++++++++++++--------
> >  1 file changed, 13 insertions(+), 8 deletions(-)
> > 
> > diff --git a/drivers/iio/magnetometer/mag3110.c b/drivers/iio/magnetometer/mag3110.c
> > index f2be4a0..90574ff 100644
> > --- a/drivers/iio/magnetometer/mag3110.c
> > +++ b/drivers/iio/magnetometer/mag3110.c
> > @@ -154,34 +154,39 @@ static int mag3110_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_MAGN: /* in 0.1 uT / LSB */
> >  			ret = mag3110_read(data, buffer);
> >  			if (ret < 0)
> > -				return ret;
> > +				goto release;
> >  			*val = sign_extend32(
> >  				be16_to_cpu(buffer[chan->scan_index]), 15);
> > -			return IIO_VAL_INT;
> > +			ret = IIO_VAL_INT;
> No break?
oops...needs one and the next case too. Thanks!


> >  		case IIO_TEMP: /* in 1 C / LSB */
> >  			mutex_lock(&data->lock);
> >  			ret = mag3110_request(data);
> >  			if (ret < 0) {
> >  				mutex_unlock(&data->lock);
> > -				return ret;
> > +				goto release;
> >  			}
> >  			ret = i2c_smbus_read_byte_data(data->client,
> >  				MAG3110_DIE_TEMP);
> >  			mutex_unlock(&data->lock);
> >  			if (ret < 0)
> > -				return ret;
> > +				goto release;
> >  			*val = sign_extend32(ret, 7);
> > -			return IIO_VAL_INT;
> > +			ret = IIO_VAL_INT;
> No break here either....
> >  		default:
> > -			return -EINVAL;
> > +			ret = -EINVAL;
> >  		}
> > +release:
> > +		iio_device_release_direct_mode(indio_dev);
> > +		return ret;
> > +
> >  	case IIO_CHAN_INFO_SCALE:
> >  		switch (chan->type) {
> >  		case IIO_MAGN:
> > 
> 

      reply	other threads:[~2016-08-15 22:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-01 15:48 [PATCH] iio: magnetometer: mag3110: claim direct mode during raw reads Alison Schofield
2016-08-15 16:04 ` Jonathan Cameron
2016-08-15 22:16   ` Alison Schofield [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=20160815221607.GA4567@d830.WORKGROUP \
    --to=amsfield22@gmail.com \
    --cc=jic23@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).