From: Jonathan Cameron <jic23@kernel.org>
To: Alexandru Ardelean <alexandru.ardelean@analog.com>
Cc: <linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<ribalda@kernel.org>,
Sergiu Cuciurean <sergiu.cuciurean@analog.com>
Subject: Re: [PATCH] iio: dac: ti-dac7612: Replace indio_dev->mlock with own device lock
Date: Sat, 29 Aug 2020 16:47:33 +0100 [thread overview]
Message-ID: <20200829164733.2a79a1cc@archlinux> (raw)
In-Reply-To: <20200826064028.51540-1-alexandru.ardelean@analog.com>
On Wed, 26 Aug 2020 09:40:28 +0300
Alexandru Ardelean <alexandru.ardelean@analog.com> wrote:
> From: Sergiu Cuciurean <sergiu.cuciurean@analog.com>
>
> As part of the general cleanup of indio_dev->mlock, this change replaces
> it with a local lock on the device's state structure.
>
> Signed-off-by: Sergiu Cuciurean <sergiu.cuciurean@analog.com>
> Signed-off-by: Alexandru Ardelean <alexandru.ardelean@analog.com>
> ---
> drivers/iio/dac/ti-dac7612.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/iio/dac/ti-dac7612.c b/drivers/iio/dac/ti-dac7612.c
> index 07c9f39d54f1..34c2aec204ef 100644
> --- a/drivers/iio/dac/ti-dac7612.c
> +++ b/drivers/iio/dac/ti-dac7612.c
> @@ -21,6 +21,7 @@ struct dac7612 {
> struct spi_device *spi;
> struct gpio_desc *loaddacs;
> uint16_t cache[2];
> + struct mutex lock;
Looks fine with the exception of my usual request for a comment explaining
lock scope.
Thanks,
Jonathan
>
> /*
> * DMA (thus cache coherency maintenance) requires the
> @@ -101,9 +102,9 @@ static int dac7612_write_raw(struct iio_dev *iio_dev,
> if (val == priv->cache[chan->channel])
> return 0;
>
> - mutex_lock(&iio_dev->mlock);
> + mutex_lock(&priv->lock);
> ret = dac7612_cmd_single(priv, chan->channel, val);
> - mutex_unlock(&iio_dev->mlock);
> + mutex_unlock(&priv->lock);
>
> return ret;
> }
> @@ -145,6 +146,8 @@ static int dac7612_probe(struct spi_device *spi)
> iio_dev->num_channels = ARRAY_SIZE(priv->cache);
> iio_dev->name = spi_get_device_id(spi)->name;
>
> + mutex_init(&priv->lock);
> +
> for (i = 0; i < ARRAY_SIZE(priv->cache); i++) {
> ret = dac7612_cmd_single(priv, i, 0);
> if (ret)
next prev parent reply other threads:[~2020-08-29 15:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 6:40 [PATCH] iio: dac: ti-dac7612: Replace indio_dev->mlock with own device lock Alexandru Ardelean
2020-08-29 15:47 ` Jonathan Cameron [this message]
2020-09-16 9:25 ` [PATCH v2] " Alexandru Ardelean
2020-09-16 17:56 ` 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=20200829164733.2a79a1cc@archlinux \
--to=jic23@kernel.org \
--cc=alexandru.ardelean@analog.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ribalda@kernel.org \
--cc=sergiu.cuciurean@analog.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).