mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Lechner <dlechner@baylibre.com>
To: Sirat <email@sirat.me>, Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org, devicetree@vger.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:39:47 -0500	[thread overview]
Message-ID: <55e92148-b5de-4fb8-af0b-9476235341bc@baylibre.com> (raw)
In-Reply-To: <CANn+LW+FNy+oCr+XskZoVS=eeCwnYvoKkFyX5fX2fbv8NbALGQ@mail.gmail.com>

On 3/21/26 6:40 PM, Sirat wrote:
> On Sat, Mar 21, 2026 at 11:22 PM Jonathan Cameron <jic23@kernel.org> wrote:
>>
>> On Fri, 20 Mar 2026 01:07:14 +0600
>> Siratul Islam <email@sirat.me> wrote:
>>
>>> Add support for the STMicroelectronics VL53L1X Time-of-Flight
>>> ranging sensor with I2C interface.
>>>
>>> Signed-off-by: Siratul Islam <email@sirat.me>
>> Hi Siratul
>>
>> Just a few minor things seeing as you are going to v7 anyway.
>> If you weren't I'd have applied some or maybe all of these as tweaks
>> whilst picking the driver up.
>>
> No problem at all.
>>
>>> diff --git a/drivers/iio/proximity/vl53l1x-i2c.c b/drivers/iio/proximity/vl53l1x-i2c.c
>>> new file mode 100644
>>> index 000000000000..771598b92e04
>>> --- /dev/null
>>> +++ b/drivers/iio/proximity/vl53l1x-i2c.c
>>> @@ -0,0 +1,820 @@
>>
> ---
>>> +     /*
>>> +      * vdd-supply is required in the DT binding but we
>>> +      * continue if it is missing to support older DTs.
>>
>> Given the driver does nothing different for an auto provided fake regulator
>> and one from DT, I'm not seeing the comment as particularly useful.
>>
>> Drop it.
>>
> Considering there is zero difference between the fake and real regulators
> in terms of functionality of this driver, should we just drop the hard
> requirement in the binding?

No, bindings should not depend on driver implementation.

>>
> 
> Thanks,
> Sirat


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

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-19 19:07 [PATCH v6 0/2] " 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
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 [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=55e92148-b5de-4fb8-af0b-9476235341bc@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

all inboxes | Powered by JetHome®