From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Nithishvelan M <mnithishvelan@gmail.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Nuno Sa <nuno.sa@analog.com>,
Michael Hennerich <Michael.Hennerich@analog.com>,
David Lechner <dlechner@baylibre.com>,
Andy Shevchenko <andy@kernel.org>,
linux-iio@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: iio: frequency: ad9832: use guard(mutex)
Date: Tue, 10 Nov 2026 19:28:50 +0200 [thread overview]
Message-ID: <avNUUuDNEiVOp_-e@ashevche-desk.local> (raw)
In-Reply-To: <20261110164711.552-1-mnithishvelan@gmail.com>
On Tue, Nov 10, 2026 at 04:47:11PM +0000, Nithishvelan M wrote:
> Use guard(mutex) to automatically manage the state lock in
> ad9832_write(). This simplifies error handling by allowing direct
> returns from each switch case and error branch, eliminating the
> manual mutex_unlock() calls and the goto error label.
Patch is okay, below some ideas for further improvements.
...
> case AD9832_PINCTRL_EN:
> st->ctrl_ss &= ~AD9832_SELSRC;
> st->ctrl_ss |= FIELD_PREP(AD9832_SELSRC, val ? 0 : 1);
This is basically FIELD_MODIFY() (and in many similar places in the driver).
...
> case AD9832_FREQ_SYM:
> if (val == 1 || val == 0) {
> st->ctrl_fp &= ~AD9832_FREQ;
> st->ctrl_fp |= FIELD_PREP(AD9832_FREQ, val ? 1 : 0);
Here ternary is unneeded, however might be still okay to have to be consistent
with the above case(s).
...
> case AD9832_PHASE_SYM:
> - if (val > 3) {
> - ret = -EINVAL;
> - break;
> - }
> + if (val > 3)
> + return -EINVAL;
In the above and here we might use FIELD_FIT(), but I haven't checked
the actual ranges.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-11-10 17:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 16:47 Nithishvelan M
2026-11-10 17:28 ` Andy Shevchenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-10-18 10:26 Melih Emik
2026-10-18 15:55 ` Joshua Crofts
2026-10-19 8:59 ` Melih Emik
2026-10-19 9:23 ` Andy Shevchenko
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=avNUUuDNEiVOp_-e@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mnithishvelan@gmail.com \
--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
all inboxes | Powered by JetHome®