public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: David Lechner <dlechner@baylibre.com>
To: Sirat <email@sirat.me>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	jic23@kernel.org, nuno.sa@analog.com, andy@kernel.org,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 2/2] iio: proximity: add driver for ST VL53L1X ToF sensor
Date: Sat, 21 Mar 2026 19:37:58 -0500	[thread overview]
Message-ID: <b1da32d2-e1f7-4fea-82a7-a40e8073a100@baylibre.com> (raw)
In-Reply-To: <CANn+LWJEJJoGQU7p2P2GrOcA_g2x7jEnvjcTJYG1hDRUnRw3UA@mail.gmail.com>

On 3/21/26 5:39 PM, Sirat wrote:
> On Sat, Mar 21, 2026 at 11:09 PM David Lechner <dlechner@baylibre.com> wrote:
>>
>> On 3/19/26 2:07 PM, Siratul Islam wrote:
>>> Add support for the STMicroelectronics VL53L1X Time-of-Flight
>>> ranging sensor with I2C interface.
>>>
...

>>> +
>>> +     ret = vl53l1x_start_ranging(data);
>>> +     if (ret)
>>> +             return ret;
>>
>> Why start ranging here? It looks like this is controlled during buffer
>> enable/disable.
>>
> The VL53L1X (unlike L0X) does not have a single-shot mode. So every
> measurement requires the device
> to be running (Autonomous mode according to the datasheet). Starting
> ranging once
> in probe allows the direct read path to work without any additional
> start/stop logic inside read_raw().
> This keeps that path simple and low-latency. The buffered/triggered
> path independently controls
> ranging via postenable/predisable, so there is no conflict.

If you do a buffered read, which stop ranging when it is done,
then how can the direct read work after that?

Can we just start and stop ranging momentarily for a direct
read?

Otherwise, is seems like we would want to have ranging always
enabled.

>>
>>
> I will address the rest of your review in the next version.
> 
> Thanks,
> Sirat


  reply	other threads:[~2026-03-22  0:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-19 19:07 [PATCH v6 0/2] iio: proximity: add driver for ST VL53L1X ToF sensor Siratul Islam
2026-03-19 19:07 ` [PATCH v6 1/2] dt-bindings: iio: proximity: add " Siratul Islam
2026-03-20  9:05   ` Krzysztof Kozlowski
2026-03-20 12:10     ` Sirat
2026-03-20 12:44       ` Krzysztof Kozlowski
2026-03-20 12:52   ` Krzysztof Kozlowski
2026-03-20 13:28     ` Sirat
2026-03-21 10:00       ` Krzysztof Kozlowski
2026-03-19 19:07 ` [PATCH v6 2/2] iio: proximity: add driver for " Siratul Islam
2026-03-20  8:38   ` Andy Shevchenko
2026-03-21 17:09   ` David Lechner
2026-03-21 22:39     ` Sirat
2026-03-22  0:37       ` David Lechner [this message]
2026-03-22 11:03         ` Jonathan Cameron
2026-03-22 13:52           ` Sirat
2026-03-24 15:17             ` Sirat
2026-03-24 17:29               ` David Lechner
2026-03-24 18:04                 ` Sirat
2026-03-21 17:21   ` Jonathan Cameron
2026-03-21 23:40     ` Sirat
2026-03-22  0:39       ` David Lechner

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=b1da32d2-e1f7-4fea-82a7-a40e8073a100@baylibre.com \
    --to=dlechner@baylibre.com \
    --cc=andy@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=email@sirat.me \
    --cc=jic23@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=robh@kernel.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