From: Jonathan Cameron <jic23@kernel.org>
To: Stepan Ionichev <sozdayvek@gmail.com>
Cc: songqiang1304521@gmail.com, dlechner@baylibre.com,
nuno.sa@analog.com, andy@kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] iio: proximity: vl53l0x: notify trigger and clear IRQ on error paths
Date: Sat, 16 May 2026 11:54:11 +0100 [thread overview]
Message-ID: <20260516115411.1e980a5c@jic23-huawei> (raw)
In-Reply-To: <20260514143711.23648-1-sozdayvek@gmail.com>
On Thu, 14 May 2026 19:37:10 +0500
Stepan Ionichev <sozdayvek@gmail.com> wrote:
> vl53l0x_trigger_handler() returns directly on the I2C read failure
> paths without calling iio_trigger_notify_done() or vl53l0x_clear_irq().
>
> A single transient i2c_smbus_read_i2c_block_data() failure (negative
> errno or a short read) therefore leaves two pieces of state behind:
>
> - iio_trigger_notify_done() never decrements the trigger's use_count,
> so iio_trigger_poll_nested() silently drops further dispatches
> (see industrialio-trigger.c, the !atomic_read(&trig->use_count)
> guard);
> - vl53l0x_clear_irq() never writes SYSTEM_INTERRUPT_CLEAR, so the
> chip keeps the DRDY interrupt asserted.
>
> The sensor's buffer mode stays wedged from then on, recoverable only
> by re-binding the driver. The sibling driver vl53l1x-i2c.c handles
> exactly the same case correctly by jumping to a "notify_and_clear_irq"
> label that always calls both helpers; mirror that here.
>
> The bogus negative-int return value cast to irqreturn_t also goes
> away as a side effect.
>
> Fixes: 762186c6e7b1 ("iio: proximity: vl53l0x-i2c: Added continuous mode support")
> Signed-off-by: Stepan Ionichev <sozdayvek@gmail.com>
Applied and marked for stable, not so much because it wedges (as probably
won't recover anyway) but more to get rid of a negative error return in an
irq handler.
> ---
> v2:
> - Drop the cited error-path code from the commit body; the diff
> already shows it (per Andy)
>
> drivers/iio/proximity/vl53l0x-i2c.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/iio/proximity/vl53l0x-i2c.c b/drivers/iio/proximity/vl53l0x-i2c.c
> index ad3e46d47..7acb94acc 100644
> --- a/drivers/iio/proximity/vl53l0x-i2c.c
> +++ b/drivers/iio/proximity/vl53l0x-i2c.c
> @@ -87,15 +87,14 @@ static irqreturn_t vl53l0x_trigger_handler(int irq, void *priv)
> ret = i2c_smbus_read_i2c_block_data(data->client,
> VL_REG_RESULT_RANGE_STATUS,
> sizeof(buffer), buffer);
> - if (ret < 0)
> - return ret;
> - else if (ret != 12)
> - return -EREMOTEIO;
> + if (ret < 0 || ret != 12)
> + goto done;
>
> scan.chan = get_unaligned_be16(&buffer[10]);
> iio_push_to_buffers_with_ts(indio_dev, &scan, sizeof(scan),
> iio_get_time_ns(indio_dev));
>
> +done:
> iio_trigger_notify_done(indio_dev->trig);
> vl53l0x_clear_irq(data);
>
next prev parent reply other threads:[~2026-05-16 10:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 14:37 Stepan Ionichev
2026-05-16 10:54 ` Jonathan Cameron [this message]
2026-05-16 15:38 ` David Lechner
2026-05-16 16:33 ` 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=20260516115411.1e980a5c@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=songqiang1304521@gmail.com \
--cc=sozdayvek@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®