From: "Nuno Sá" <noname.nuno@gmail.com>
To: Gabriel Shahrouzi <gshahrouzi@gmail.com>,
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,
sonic.zhang@analog.com, vapier@gentoo.org
Cc: skhan@linuxfoundation.org,
kernelmentees@lists.linuxfoundation.org, stable@vger.kernel.org
Subject: Re: [PATCH] iio: adc: Revoke valid channel for error path
Date: Thu, 17 Apr 2025 11:06:51 +0100 [thread overview]
Message-ID: <fb712c034eda0d5d711a90a00b6382315fb5f929.camel@gmail.com> (raw)
In-Reply-To: <20250415182038.523186-1-gshahrouzi@gmail.com>
On Tue, 2025-04-15 at 14:20 -0400, Gabriel Shahrouzi wrote:
> According to the datasheet on page 9 under the channel selection table,
> all devices (AD7816/7/8) are able to use the channel marked as 7. This
> channel is used for diagnostic purposes by routing the internal 1.23V
> bandgap source through the MUX to the input of the ADC.
>
> Replace checking for string equality with checking for the same chip ID
> to reduce time complexity.
>
> Group invalid channels for all devices together because they are
> processed the same way.
>
> Fixes: 7924425db04a ("staging: iio: adc: new driver for AD7816 devices")
> Cc: stable@vger.kernel.org
> Signed-off-by: Gabriel Shahrouzi <gshahrouzi@gmail.com>
> ---
> drivers/staging/iio/adc/ad7816.c | 15 +++++----------
> 1 file changed, 5 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/staging/iio/adc/ad7816.c
> b/drivers/staging/iio/adc/ad7816.c
> index 6c14d7bcdd675..d880fe0257697 100644
> --- a/drivers/staging/iio/adc/ad7816.c
> +++ b/drivers/staging/iio/adc/ad7816.c
> @@ -186,17 +186,12 @@ static ssize_t ad7816_store_channel(struct device *dev,
> if (ret)
> return ret;
>
> - if (data > AD7816_CS_MAX && data != AD7816_CS_MASK) {
> - dev_err(&chip->spi_dev->dev, "Invalid channel id %lu for
> %s.\n",
> - data, indio_dev->name);
> - return -EINVAL;
> - } else if (strcmp(indio_dev->name, "ad7818") == 0 && data > 1) {
> - dev_err(&chip->spi_dev->dev,
> - "Invalid channel id %lu for ad7818.\n", data);
> - return -EINVAL;
> - } else if (strcmp(indio_dev->name, "ad7816") == 0 && data > 0) {
> + if (data != AD7816_CS_MASK &&
> + (data > AD7816_CS_MAX ||
> + (chip->id == ID_AD7818 && data > 1) ||
> + (chip->id == ID_AD7816 && data > 0))) {
> dev_err(&chip->spi_dev->dev,
> - "Invalid channel id %lu for ad7816.\n", data);
> + "Invalid channel id %lu for %s.\n", data, indio_dev-
> >name);
> return -EINVAL;
> }
Hmm, maybe I'm missing something but the code just looks the same as before
(from a functionality point of view)? I'm really not seeing any fix...
Having said the above, not sure if grouping helps with readability. But I do
agree with moving from string comparison to use chip->id. And we also have
redundants 'else'
- Nuno Sá
next prev parent reply other threads:[~2025-04-17 10:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 18:20 [PATCH] iio: adc: Revoke valid channel for error path Gabriel Shahrouzi
2025-04-17 10:06 ` Nuno Sá [this message]
2025-04-17 12:53 ` Gabriel Shahrouzi
2025-04-17 14:02 ` Nuno Sá
2025-04-17 17:08 ` Gabriel Shahrouzi
2025-04-18 8:46 ` Nuno Sá
2025-04-18 13:28 ` 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=fb712c034eda0d5d711a90a00b6382315fb5f929.camel@gmail.com \
--to=noname.nuno@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=gregkh@linuxfoundation.org \
--cc=gshahrouzi@gmail.com \
--cc=jic23@kernel.org \
--cc=kernelmentees@lists.linuxfoundation.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=skhan@linuxfoundation.org \
--cc=sonic.zhang@analog.com \
--cc=stable@vger.kernel.org \
--cc=vapier@gentoo.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;
as well as URLs for NNTP newsgroup(s).