From: Jonathan Cameron <jic23@kernel.org>
To: Batu Ada Tutkun <batuadatutkun@gmail.com>
Cc: "David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-iio@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: iio: frequency: ad9834: use guard() for mutex locking
Date: Wed, 1 Jul 2026 21:42:44 +0100 [thread overview]
Message-ID: <20260701214244.11dc26f7@jic23-huawei> (raw)
In-Reply-To: <20260625120456.1267-1-batuadatutkun@gmail.com>
On Thu, 25 Jun 2026 15:04:55 +0300
Batu Ada Tutkun <batuadatutkun@gmail.com> wrote:
> Replace manual mutex_lock()/mutex_unlock() pairs with guard(mutex) in
> ad9834_write() and ad9834_store_wavetype(). The mutex is now released
> automatically when each function returns, removing the need for
> explicit unlock calls.
>
> Signed-off-by: Batu Ada Tutkun <batuadatutkun@gmail.com>
Whilst we aren't taking this forwards, a few comments inline for future
reference.
> ---
> drivers/staging/iio/frequency/ad9834.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/staging/iio/frequency/ad9834.c b/drivers/staging/iio/frequency/ad9834.c
> index bdb2580e2..f15819eaf 100644
> --- a/drivers/staging/iio/frequency/ad9834.c
> +++ b/drivers/staging/iio/frequency/ad9834.c
> @@ -17,6 +17,7 @@
> #include <linux/regulator/consumer.h>
> #include <linux/err.h>
> #include <linux/module.h>
> +#include <linux/mutex.h>
I'm guessing cleanup.h is missing as well. You should have both
when guard(mutex) is is in use.
> #include <asm/div64.h>
>
> #include <linux/iio/iio.h>
> @@ -152,7 +153,7 @@ static ssize_t ad9834_write(struct device *dev,
> if (ret)
> return ret;
>
> - mutex_lock(&st->lock);
> + guard(mutex)(&st->lock);
> switch ((u32)this_attr->address) {
> case AD9834_REG_FREQ0:
> case AD9834_REG_FREQ1:
> @@ -210,7 +211,6 @@ static ssize_t ad9834_write(struct device *dev,
> default:
> ret = -ENODEV;
The big advantage of using guard() is not removing mutex_unlock() but
instead that you can use simpler code flow. Here you should return early.
There are a lot of error returns in this function and it may even
make sense to return len early if no error.
> }
> - mutex_unlock(&st->lock);
>
> return ret ? ret : len;
> }
> @@ -226,7 +226,7 @@ static ssize_t ad9834_store_wavetype(struct device *dev,
> int ret = 0;
> bool is_ad9833_7 = (st->devid == ID_AD9833) || (st->devid == ID_AD9837);
>
> - mutex_lock(&st->lock);
> + guard(mutex)(&st->lock);
>
> switch ((u32)this_attr->address) {
> case 0:
> @@ -269,7 +269,6 @@ static ssize_t ad9834_store_wavetype(struct device *dev,
> st->data = cpu_to_be16(AD9834_REG_CMD | st->control);
> ret = spi_sync(st->spi, &st->msg);
> }
> - mutex_unlock(&st->lock);
Similar applies in this function where there are a lot of paths
that can become early error returns if guard() is used.
Jonathan
>
> return ret ? ret : len;
> }
prev parent reply other threads:[~2026-07-01 20:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-25 12:04 [PATCH] staging: iio: frequency: ad9834: use guard() for mutex locking Batu Ada Tutkun
2026-06-25 12:40 ` Greg Kroah-Hartman
2026-06-25 12:43 ` Joshua Crofts
2026-07-01 20:42 ` 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=20260701214244.11dc26f7@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=batuadatutkun@gmail.com \
--cc=dlechner@baylibre.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=nuno.sa@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