From: Jonathan Cameron <jic23@kernel.org>
To: Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Alison Schofield <amsfield22@gmail.com>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: magnetometer: mag3110: claim direct mode during raw writes
Date: Sat, 21 Jan 2017 12:21:16 +0000 [thread overview]
Message-ID: <8ef429c6-621e-83a3-4991-edaf0bfc8775@kernel.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1701211042580.30223@pmeerw.net>
On 21/01/17 09:43, Peter Meerwald-Stadler 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 writes.
>
> looks good,
> Acked-by: Peter Meerwald-Stadler <pmeerw@pmeerw.net>
Applied to the togreg branch of iio.git - initially pushed out as testing etc..
Jonathan
>
>> Signed-off-by: Alison Schofield <amsfield22@gmail.com>
>> ---
>> drivers/iio/magnetometer/mag3110.c | 30 ++++++++++++++++++++----------
>> 1 file changed, 20 insertions(+), 10 deletions(-)
>>
>> diff --git a/drivers/iio/magnetometer/mag3110.c b/drivers/iio/magnetometer/mag3110.c
>> index f2b3bd7..b4f643f 100644
>> --- a/drivers/iio/magnetometer/mag3110.c
>> +++ b/drivers/iio/magnetometer/mag3110.c
>> @@ -222,29 +222,39 @@ static int mag3110_write_raw(struct iio_dev *indio_dev,
>> int val, int val2, long mask)
>> {
>> struct mag3110_data *data = iio_priv(indio_dev);
>> - int rate;
>> + int rate, ret;
>>
>> - if (iio_buffer_enabled(indio_dev))
>> - return -EBUSY;
>> + ret = iio_device_claim_direct_mode(indio_dev);
>> + if (ret)
>> + return ret;
>>
>> switch (mask) {
>> case IIO_CHAN_INFO_SAMP_FREQ:
>> rate = mag3110_get_samp_freq_index(data, val, val2);
>> - if (rate < 0)
>> - return -EINVAL;
>> + if (rate < 0) {
>> + ret = -EINVAL;
>> + break;
>> + }
>>
>> data->ctrl_reg1 &= ~MAG3110_CTRL_DR_MASK;
>> data->ctrl_reg1 |= rate << MAG3110_CTRL_DR_SHIFT;
>> - return i2c_smbus_write_byte_data(data->client,
>> + ret = i2c_smbus_write_byte_data(data->client,
>> MAG3110_CTRL_REG1, data->ctrl_reg1);
>> + break;
>> case IIO_CHAN_INFO_CALIBBIAS:
>> - if (val < -10000 || val > 10000)
>> - return -EINVAL;
>> - return i2c_smbus_write_word_swapped(data->client,
>> + if (val < -10000 || val > 10000) {
>> + ret = -EINVAL;
>> + break;
>> + }
>> + ret = i2c_smbus_write_word_swapped(data->client,
>> MAG3110_OFF_X + 2 * chan->scan_index, val << 1);
>> + break;
>> default:
>> - return -EINVAL;
>> + ret = -EINVAL;
>> + break;
>> }
>> + iio_device_release_direct_mode(indio_dev);
>> + return ret;
>> }
>>
>> static irqreturn_t mag3110_trigger_handler(int irq, void *p)
>>
>
prev parent reply other threads:[~2017-01-21 12:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 20:39 Alison Schofield
2017-01-21 9:43 ` Peter Meerwald-Stadler
2017-01-21 12:21 ` 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=8ef429c6-621e-83a3-4991-edaf0bfc8775@kernel.org \
--to=jic23@kernel.org \
--cc=amsfield22@gmail.com \
--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
all inboxes | Powered by JetHome®