From: Dan Carpenter <dan.carpenter@linaro.org>
To: Gabriel Shahrouzi <gshahrouzi@gmail.com>
Cc: gregkh@linuxfoundation.org, jic23@kernel.org, lars@metafoo.de,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-staging@lists.linux.dev, Michael.Hennerich@analog.com,
skhan@linuxfoundation.org, linux-kernel-mentees@lists.linux.dev
Subject: Re: [PATCH v2 3/3] staging: iio: ad9832: Add minor improvements to ad9832_write_powerdown
Date: Tue, 22 Apr 2025 13:08:25 +0300 [thread overview]
Message-ID: <e712ec88-d925-4a73-8df4-ca3387a903fd@stanley.mountain> (raw)
In-Reply-To: <20250420174725.887242-4-gshahrouzi@gmail.com>
On Sun, Apr 20, 2025 at 01:47:25PM -0400, Gabriel Shahrouzi wrote:
> Minimize size of type that needs to be used by replacing unsigned long
> with bool. Avoid redundancy by checking if cached power state is the
> same as the one requested.
>
> Signed-off-by: Gabriel Shahrouzi <gshahrouzi@gmail.com>
> ---
> drivers/staging/iio/frequency/ad9832.c | 18 ++++++++++++------
> 1 file changed, 12 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/staging/iio/frequency/ad9832.c b/drivers/staging/iio/frequency/ad9832.c
> index a8fc20379efed..2ab6026d56b5c 100644
> --- a/drivers/staging/iio/frequency/ad9832.c
> +++ b/drivers/staging/iio/frequency/ad9832.c
> @@ -173,13 +173,19 @@ static ssize_t ad9832_write_powerdown(struct device *dev, struct device_attribut
> struct iio_dev *indio_dev = dev_to_iio_dev(dev);
> struct ad9832_state *st = iio_priv(indio_dev);
> int ret;
> - unsigned long val;
> + bool val;
> + bool cur;
>
> - ret = kstrtoul(buf, 10, &val);
> + ret = kstrtobool(buf, &val);
> if (ret)
> - goto error_ret;
> + return ret;
Fold this whole thing into patch 2. Don't write something and then fix
it in the next patch.
>
> mutex_lock(&st->lock);
> +
> + cur = !!(st->ctrl_src & AD9832_SLEEP);
> + if (val == cur)
> + goto unlock;
> +
> if (val)
> st->ctrl_src |= AD9832_SLEEP;
> else
> @@ -189,10 +195,10 @@ static ssize_t ad9832_write_powerdown(struct device *dev, struct device_attribut
> st->data = cpu_to_be16((AD9832_CMD_SLEEPRESCLR << CMD_SHIFT) |
> st->ctrl_src);
> ret = spi_sync(st->spi, &st->msg);
> - mutex_unlock(&st->lock);
>
> -error_ret:
> - return ret ? ret : len;
> +unlock:
> + mutex_unlock(&st->lock);
> + return len;
This should still be:
return ret ? ret : len;
regards,
dan carpenter
next prev parent reply other threads:[~2025-04-22 10:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-20 17:47 [PATCH v2 0/3] Fix and refactor output disable logic Gabriel Shahrouzi
2025-04-20 17:47 ` [PATCH v2 1/3] iio: frequency: Use SLEEP bit instead of RESET to disable output Gabriel Shahrouzi
2025-04-20 17:47 ` [PATCH v2 2/3] staging: iio: ad9832: Refactor powerdown control Gabriel Shahrouzi
2025-04-20 17:47 ` [PATCH v2 3/3] staging: iio: ad9832: Add minor improvements to ad9832_write_powerdown Gabriel Shahrouzi
2025-04-22 10:08 ` Dan Carpenter [this message]
2025-04-22 16:14 ` Gabriel Shahrouzi
2025-04-22 16:25 ` Gabriel Shahrouzi
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=e712ec88-d925-4a73-8df4-ca3387a903fd@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=Michael.Hennerich@analog.com \
--cc=gregkh@linuxfoundation.org \
--cc=gshahrouzi@gmail.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=skhan@linuxfoundation.org \
/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