From: Jonathan Cameron <jic23@kernel.org>
To: Donggeun Yoo <donggeunyoo.kernel@gmail.com>
Cc: "Song Qiang" <songqiang1304521@gmail.com>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Abhash Jha" <abhashkumarjha123@gmail.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: proximity: vl53l0x-i2c: claim direct mode for raw reads
Date: Mon, 7 Sep 2026 02:25:43 +0100 [thread overview]
Message-ID: <20260907022543.09b544c8@jic23-huawei> (raw)
In-Reply-To: <20260901152126.533902-1-donggeunyoo.kernel@gmail.com>
On Wed, 2 Sep 2026 00:21:26 +0900
Donggeun Yoo <donggeunyoo.kernel@gmail.com> wrote:
> vl53l0x_read_raw() starts a single-shot ranging measurement and reads
> back the result. Once the triggered buffer is enabled the sensor runs in
> continuous mode and its data-ready interrupt is routed to the trigger,
> so a concurrent in_distance_raw read disturbs the streaming setup and
> never gets its completion, returning -ETIMEDOUT.
>
> The original submission claimed direct mode here, but it was dropped
> during review because the driver had no buffer support at the time [1].
> Continuous (buffered) mode was later added without restoring the
> claim [2], reintroducing the conflict.
>
> Reject direct reads while buffered capture is active by claiming direct
> mode around the measurement, as the vl53l1x sibling already does.
>
> Fixes: 762186c6e7b1 ("iio: proximity: vl53l0x-i2c: Added continuous mode support")
> Link: https://lore.kernel.org/linux-iio/20180911160300.GA9212@himanshu-Vostro-3559/ [1]
> Link: https://lore.kernel.org/linux-iio/20240909101508.263085-3-abhashkumarjha123@gmail.com/ [2]
> Signed-off-by: Donggeun Yoo <donggeunyoo.kernel@gmail.com>
Applied to the fixes-togreg branch of iio.git.
Thanks,
Jonathan
> ---
> Only compile-tested; I don't have VL53L0X hardware to exercise the race
> yet. The change mirrors the existing vl53l1x sibling.
>
> drivers/iio/proximity/vl53l0x-i2c.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/iio/proximity/vl53l0x-i2c.c b/drivers/iio/proximity/vl53l0x-i2c.c
> index 9fe14ceb8be7..173e69753df7 100644
> --- a/drivers/iio/proximity/vl53l0x-i2c.c
> +++ b/drivers/iio/proximity/vl53l0x-i2c.c
> @@ -219,7 +219,10 @@ static int vl53l0x_read_raw(struct iio_dev *indio_dev,
>
> switch (mask) {
> case IIO_CHAN_INFO_RAW:
> + if (!iio_device_claim_direct(indio_dev))
> + return -EBUSY;
> ret = vl53l0x_read_proximity(data, chan, val);
> + iio_device_release_direct(indio_dev);
> if (ret < 0)
> return ret;
>
prev parent reply other threads:[~2026-09-07 1:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 15:21 [PATCH] iio: proximity: vl53l0x-i2c: claim direct mode for raw reads Donggeun Yoo
2026-09-07 1:25 ` Jonathan Cameron [this message]
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=20260907022543.09b544c8@jic23-huawei \
--to=jic23@kernel.org \
--cc=abhashkumarjha123@gmail.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=donggeunyoo.kernel@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=songqiang1304521@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