From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Ruslan Valiyev <linuxoid@gmail.com>
Cc: lars@metafoo.de, Michael.Hennerich@analog.com, jic23@kernel.org,
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] staging: iio: adc: ad7816: add timeout to busy-wait loop
Date: Thu, 26 Feb 2026 10:01:11 +0200 [thread overview]
Message-ID: <aZ_9x4q5BZRJi3ue@smile.fi.intel.com> (raw)
In-Reply-To: <20260226052615.65734-1-linuxoid@gmail.com>
On Thu, Feb 26, 2026 at 05:26:15AM +0000, Ruslan Valiyev wrote:
> The ad7816_spi_read() function polls the busy GPIO pin in a tight
> loop without any timeout. If the hardware fails to deassert the
> busy signal, the kernel hangs indefinitely in an unbounded
> busy-wait.
>
> Replace the open-coded while/cpu_relax() loop with
> read_poll_timeout() which polls every 5 us and returns -ETIMEDOUT
> after 1 ms. Per the AD7816 datasheet the maximum conversion time
> is 27 us (temperature channel), so 1 ms provides generous margin.
>
> Also handle the case where gpiod_get_value() returns a negative
> error code, which the original loop silently treated as not-busy.
...
> - while (gpiod_get_value(chip->busy_pin))
> - cpu_relax();
> + int val;
> +
> + ret = read_poll_timeout(gpiod_get_value, val, val <= 0,
> + 5, 1000, false, chip->busy_pin);
> + if (val < 0)
> + return val;
> + if (ret)
> + return ret;
Have you able to test this?
Have you investigated the code? It was an atomic, now it's sleeping.
This is a huge behavioural change. See my first Q.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-02-26 8:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 5:26 Ruslan Valiyev
2026-02-26 8:01 ` Andy Shevchenko [this message]
2026-02-26 8:25 ` Ruslan Valiyev
2026-02-26 9:20 ` Dan Carpenter
2026-02-26 8:25 ` [PATCH v2] " Ruslan Valiyev
2026-02-26 9:15 ` Andy Shevchenko
2026-02-26 9:29 ` Ruslan Valiyev
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=aZ_9x4q5BZRJi3ue@smile.fi.intel.com \
--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=linuxoid@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®