From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Taha Narimani <tahanarimani3443@gmail.com>
Cc: jic23@kernel.org, lars@metafoo.de, Michael.Hennerich@analog.com,
gregkh@linuxfoundation.org, dlechner@baylibre.com,
nuno.sa@analog.com, andy@kernel.org, linux-iio@vger.kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: iio: adc: ad7816: Use devm_gpiod_get_optional() for busy GPIO
Date: Wed, 3 Jun 2026 12:26:11 +0300 [thread overview]
Message-ID: <ah_zMybQBDHakXpX@ashevche-desk.local> (raw)
In-Reply-To: <20260603123333.5608-1-tahanarimani3443@gmail.com>
On Wed, Jun 03, 2026 at 12:33:33PM +0000, Taha Narimani wrote:
> The driver currently utilizes devm_gpiod_get() for the 'busy' line,
> which makes the GPIO mandatory. However, the busy pin is hardware-optional
> depending on the specific board configuration.
>
> Switch to devm_gpiod_get_optional() to allow boards that do not have
> this pin wired up to still probe the driver successfully, and remove
> the redundant conditional chip-ID check since the optional API handles
> missing descriptors gracefully.
...
> - if (chip->id == ID_AD7817) {
> + if (chip->busy_pin) {
If we get GPIO optional, this check wouldn't be necessary anymore as the below
should return 0 IIRC in this case.
> while (gpiod_get_value(chip->busy_pin))
> cpu_relax();
> }
> + chip->busy_pin = devm_gpiod_get_optional(&spi_dev->dev, "busy",
> + GPIOD_IN);
Make it a single line. Perhaps with a help of
struct device *dev = &spi_dev->dev;
added to the top of the function.
> + if (IS_ERR(chip->busy_pin)) {
> + ret = PTR_ERR(chip->busy_pin);
> + dev_err(&spi_dev->dev, "Failed to request busy GPIO: %d\n",
> + ret);
> + return ret;
You can't do that, it will spam bootlog very quickly if this GPIO is deferred
and never appears. The proper way is to
return dev_err_probe(dev, PTR_ERR(chip->busy_pin), "...");
> }
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-06-03 9:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 12:33 Taha Narimani
2026-06-03 9:13 ` Joshua Crofts
2026-06-03 9:27 ` Andy Shevchenko
2026-06-03 9:26 ` Andy Shevchenko [this message]
2026-06-03 10:20 ` Dan Carpenter
2026-06-03 10:37 ` Andy Shevchenko
2026-06-03 10:54 ` Dan Carpenter
2026-06-03 10:52 ` 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=ah_zMybQBDHakXpX@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=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=nuno.sa@analog.com \
--cc=tahanarimani3443@gmail.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®