[PATCH v5 0/2] iio: proximity: move LIDAR-Lite out of trivial-devices and add Garmin fallback

[PATCH v5 0/2] iio: proximity: move LIDAR-Lite out of trivial-devices and add Garmin fallback

[Rodrigo Gobbi]

This series moves the LIDAR-Lite v2 binding out of trivial-devices
into a dedicated schema, documenting the power-enable, power-supply
and status-output interrupt properties that trivial-devices.yaml has
no way to express.

It then adds the Garmin LIDAR-Lite v3 as a fallback compatible in a
separate patch, since it is pin-compatible with the v2 and already
matched by the driver, so no driver changes are needed.
---
Changelog:
v5:
  - split into two commits, one for moving lidar out of trivial and
  one for adding a fallback compatible for LIDAR-Lite v3;
  - minor changes at yaml like: title, description, adding irq prop;
  - improve commit msgs for covering the vendor acquisition and PWM mode;
v4: https://lore.kernel.org/all/20260714215433.41259-1-rodrigo.gobbi.7@gmail.com/
v3: https://lore.kernel.org/all/20251102221643.9966-1-rodrigo.gobbi.7@gmail.com/
v2: https://lore.kernel.org/all/20250801224112.135918-1-rodrigo.gobbi.7@gmail.com/
v1: https://lore.kernel.org/all/20250701223341.36835-1-rodrigo.gobbi.7@gmail.com/
---
Rodrigo Gobbi (2):
  dt-bindings: iio: proximity: move LIDAR-Lite v2 out of trivial-devices
  dt-bindings: iio: proximity: document LIDAR-Lite v3 fallback
    compatible

 .../proximity/pulsedlight,lidar-lite-v2.yaml  | 70 +++++++++++++++++++
 .../devicetree/bindings/trivial-devices.yaml  |  2 -
 2 files changed, 70 insertions(+), 2 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/iio/proximity/pulsedlight,lidar-lite-v2.yaml

-- 
2.48.1

[PATCH v5 1/2] dt-bindings: iio: proximity: move LIDAR-Lite v2 out of trivial-devices

[Rodrigo Gobbi]

The PulsedLight LIDAR-Lite v2 is currently described as a trivial device,
but it is not one: besides the I2C interface it exposes a power-enable
pin and a mode-control pin.

The mode-control pin can trigger acquisitions and report the measured
distance through a PWM signal, entirely bypassing I2C. That usage is
bidirectional and non-cyclic, so it doesn't map onto any existing
binding for describing pin behaviour, and is intentionally left
undocumented here. The same pin can, however, also be used as a plain
status output while I2C remains the active interface, which is
described through the new interrupts property.

Move the device to a dedicated binding file and document the
power-enable, power-supply and interrupt properties that
trivial-devices.yaml has no way to express.

Signed-off-by: Rodrigo Gobbi <rodrigo.gobbi.7@gmail.com>
---
 .../proximity/pulsedlight,lidar-lite-v2.yaml  | 64 +++++++++++++++++++
 .../devicetree/bindings/trivial-devices.yaml  |  2 -
 2 files changed, 64 insertions(+), 2 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/iio/proximity/pulsedlight,lidar-lite-v2.yaml

diff --git a/Documentation/devicetree/bindings/iio/proximity/pulsedlight,lidar-lite-v2.yaml b/Documentation/devicetree/bindings/iio/proximity/pulsedlight,lidar-lite-v2.yaml
new file mode 100644
index 000000000000..e19c8d166b81
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/proximity/pulsedlight,lidar-lite-v2.yaml
@@ -0,0 +1,64 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iio/proximity/pulsedlight,lidar-lite-v2.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Pulsedlight LIDAR-Lite v2 range-finding sensor
+
+maintainers:
+  - Matt Ranostay <mranostay@gmail.com>
+
+description: |
+  This binding covers the I2C interface of the Pulsedlight LIDAR-Lite v2
+  laser rangefinder.
+
+  Besides I2C, the mode control pin can also trigger acquisitions and
+  report the measured distance through a PWM signal, without using I2C
+  at all. That usage is bidirectional and non-cyclic, and is not
+  described by this binding. The same pin can also be used, while I2C
+  remains the active interface, as a plain status output signalling
+  when an acquisition has completed.
+
+  Datasheet:
+    https://github.com/PulsedLight3D/LIDAR-Lite-Documentation/blob/master/Docs/LIDAR-Lite-v2-Docs.pdf
+
+properties:
+  compatible:
+    const: pulsedlight,lidar-lite-v2
+
+  reg:
+    maxItems: 1
+
+  powerdown-gpios:
+    description: GPIO that can be driven low to shut off power to the device.
+    maxItems: 1
+
+  vdd-supply: true
+
+  interrupts:
+    description:
+      Mode control pin used as a status output, driven while the device is
+      busy performing an acquisition. Can be used to signal completion
+      instead of polling over I2C.
+    maxItems: 1
+
+required:
+  - compatible
+  - reg
+  - vdd-supply
+
+additionalProperties: false
+
+examples:
+  - |
+    i2c {
+        #address-cells = <1>;
+        #size-cells = <0>;
+        lidar@62 {
+            compatible = "pulsedlight,lidar-lite-v2";
+            reg = <0x62>;
+            vdd-supply = <&vdd_5v0>;
+        };
+    };
+...
diff --git a/Documentation/devicetree/bindings/trivial-devices.yaml b/Documentation/devicetree/bindings/trivial-devices.yaml
index 435c4baab436..74b640c48598 100644
--- a/Documentation/devicetree/bindings/trivial-devices.yaml
+++ b/Documentation/devicetree/bindings/trivial-devices.yaml
@@ -396,8 +396,6 @@ properties:
           - onnn,adt7462
             # 48-Lane, 12-Port PCI Express Gen 2 (5.0 GT/s) Switch
           - plx,pex8648
-            # Pulsedlight LIDAR range-finding sensor
-          - pulsedlight,lidar-lite-v2
             # Renesas HS3001 Temperature and Relative Humidity Sensors
           - renesas,hs3001
             # Renesas ISL29501 time-of-flight sensor
-- 
2.48.1

Re: [PATCH v5 1/2] dt-bindings: iio: proximity: move LIDAR-Lite v2 out of trivial-devices

[Krzysztof Kozlowski]

On Mon, Aug 10, 2026 at 04:18:40PM -0300, Rodrigo Gobbi wrote:
> The PulsedLight LIDAR-Lite v2 is currently described as a trivial device,
> but it is not one: besides the I2C interface it exposes a power-enable
> pin and a mode-control pin.
> 
> The mode-control pin can trigger acquisitions and report the measured
> distance through a PWM signal, entirely bypassing I2C. That usage is
> bidirectional and non-cyclic, so it doesn't map onto any existing
> binding for describing pin behaviour, and is intentionally left
> undocumented here. The same pin can, however, also be used as a plain
> status output while I2C remains the active interface, which is
> described through the new interrupts property.
> 
> Move the device to a dedicated binding file and document the
> power-enable, power-supply and interrupt properties that
> trivial-devices.yaml has no way to express.
> 
> Signed-off-by: Rodrigo Gobbi <rodrigo.gobbi.7@gmail.com>
> ---
>  .../proximity/pulsedlight,lidar-lite-v2.yaml  | 64 +++++++++++++++++++
>  .../devicetree/bindings/trivial-devices.yaml  |  2 -
>  2 files changed, 64 insertions(+), 2 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/iio/proximity/pulsedlight,lidar-lite-v2.yaml

Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>

Best regards,
Krzysztof

Re: [PATCH v5 1/2] dt-bindings: iio: proximity: move LIDAR-Lite v2 out of trivial-devices

[Jonathan Cameron]

On Mon, 10 Aug 2026 16:18:40 -0300
Rodrigo Gobbi <rodrigo.gobbi.7@gmail.com> wrote:

> The PulsedLight LIDAR-Lite v2 is currently described as a trivial device,
> but it is not one: besides the I2C interface it exposes a power-enable
> pin and a mode-control pin.
> 
> The mode-control pin can trigger acquisitions and report the measured
> distance through a PWM signal, entirely bypassing I2C. That usage is
> bidirectional and non-cyclic, so it doesn't map onto any existing
> binding for describing pin behaviour, and is intentionally left
> undocumented here. The same pin can, however, also be used as a plain
> status output while I2C remains the active interface, which is
> described through the new interrupts property.
> 
> Move the device to a dedicated binding file and document the
> power-enable, power-supply and interrupt properties that
> trivial-devices.yaml has no way to express.
> 
> Signed-off-by: Rodrigo Gobbi <rodrigo.gobbi.7@gmail.com>
> ---
>  .../proximity/pulsedlight,lidar-lite-v2.yaml  | 64 +++++++++++++++++++
>  .../devicetree/bindings/trivial-devices.yaml  |  2 -
>  2 files changed, 64 insertions(+), 2 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/iio/proximity/pulsedlight,lidar-lite-v2.yaml
> 
> diff --git a/Documentation/devicetree/bindings/iio/proximity/pulsedlight,lidar-lite-v2.yaml b/Documentation/devicetree/bindings/iio/proximity/pulsedlight,lidar-lite-v2.yaml
> new file mode 100644
> index 000000000000..e19c8d166b81
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/proximity/pulsedlight,lidar-lite-v2.yaml
> @@ -0,0 +1,64 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/iio/proximity/pulsedlight,lidar-lite-v2.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Pulsedlight LIDAR-Lite v2 range-finding sensor
> +
> +maintainers:
> +  - Matt Ranostay <mranostay@gmail.com>
I'll need an Ack or Reviewed-by from Matt for this. If Matt either doesn't
reply for a while, or isn't happy to take on this much fuller binding,
is it something you'd consider putting yourself down for?

Otherwise LGTM

Thanks,

Jonathan

Re: [PATCH v5 1/2] dt-bindings: iio: proximity: move LIDAR-Lite v2 out of trivial-devices

[Matt Ranostay]

On Wednesday, August 12th, 2026 at 12:35, Jonathan Cameron <jic23@kernel.org> wrote:

> On Mon, 10 Aug 2026 16:18:40 -0300
> Rodrigo Gobbi <rodrigo.gobbi.7@gmail.com> wrote:
> 
> > The PulsedLight LIDAR-Lite v2 is currently described as a trivial device,
> > but it is not one: besides the I2C interface it exposes a power-enable
> > pin and a mode-control pin.
> >
> > The mode-control pin can trigger acquisitions and report the measured
> > distance through a PWM signal, entirely bypassing I2C. That usage is
> > bidirectional and non-cyclic, so it doesn't map onto any existing
> > binding for describing pin behaviour, and is intentionally left
> > undocumented here. The same pin can, however, also be used as a plain
> > status output while I2C remains the active interface, which is
> > described through the new interrupts property.
> >
> > Move the device to a dedicated binding file and document the
> > power-enable, power-supply and interrupt properties that
> > trivial-devices.yaml has no way to express.
> >
> > Signed-off-by: Rodrigo Gobbi <rodrigo.gobbi.7@gmail.com>
> > ---
> >  .../proximity/pulsedlight,lidar-lite-v2.yaml  | 64 +++++++++++++++++++
> >  .../devicetree/bindings/trivial-devices.yaml  |  2 -
> >  2 files changed, 64 insertions(+), 2 deletions(-)
> >  create mode 100644 Documentation/devicetree/bindings/iio/proximity/pulsedlight,lidar-lite-v2.yaml
> >
> > diff --git a/Documentation/devicetree/bindings/iio/proximity/pulsedlight,lidar-lite-v2.yaml b/Documentation/devicetree/bindings/iio/proximity/pulsedlight,lidar-lite-v2.yaml
> > new file mode 100644
> > index 000000000000..e19c8d166b81
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/iio/proximity/pulsedlight,lidar-lite-v2.yaml
> > @@ -0,0 +1,64 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/iio/proximity/pulsedlight,lidar-lite-v2.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: Pulsedlight LIDAR-Lite v2 range-finding sensor
> > +
> > +maintainers:
> > +  - Matt Ranostay <mranostay@gmail.com>

I really don't use my gmail address anymore. Would be ideal if it was changed matt@ranostay.sg 
Other than that don't have any issues.

Thanks,

Matt


> I'll need an Ack or Reviewed-by from Matt for this. If Matt either doesn't
> reply for a while, or isn't happy to take on this much fuller binding,
> is it something you'd consider putting yourself down for?
> 
> Otherwise LGTM
> 
> Thanks,
> 
> Jonathan
> 

Re: [PATCH v5 1/2] dt-bindings: iio: proximity: move LIDAR-Lite v2 out of trivial-devices

[Rodrigo Gobbi]

On 8/12/26 07:11, Matt Ranostay wrote:

>> >
>> > diff --git a/Documentation/devicetree/bindings/iio/proximity/pulsedlight,lidar-lite-v2.yaml b/Documentation/devicetree/bindings/iio/proximity/pulsedlight,lidar-lite-v2.yaml
>> > new file mode 100644
>> > index 000000000000..e19c8d166b81
>> > --- /dev/null
>> > +++ b/Documentation/devicetree/bindings/iio/proximity/pulsedlight,lidar-lite-v2.yaml
>> > @@ -0,0 +1,64 @@
>> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> > +%YAML 1.2
>> > +---
>> > +$id: http://devicetree.org/schemas/iio/proximity/pulsedlight,lidar-lite-v2.yaml#
>> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> > +
>> > +title: Pulsedlight LIDAR-Lite v2 range-finding sensor
>> > +
>> > +maintainers:
>> > +  - Matt Ranostay <mranostay@gmail.com>
> 
> I really don't use my gmail address anymore. Would be ideal if it was changed matt@ranostay.sg 
> Other than that don't have any issues.
> 
> Thanks,
> 
> Matt

Thanks Matt, I will send a v6 fixing the e-mail. Since you're fine with it, would you
mind sending a formal Reviewed-by/Acked-by?

> 
> 
>> I'll need an Ack or Reviewed-by from Matt for this. If Matt either doesn't
>> reply for a while, or isn't happy to take on this much fuller binding,
>> is it something you'd consider putting yourself down for?
>> 
>> Otherwise LGTM
>> 
>> Thanks,
>> 
>> Jonathan

I'm happy to be added as a second maintainer for this binding,
(I can add myself at v6) but I'd rather defer to Matt as the
primary one for now.
Thanks!
Rodrigo.

Re: [PATCH v5 1/2] dt-bindings: iio: proximity: move LIDAR-Lite v2 out of trivial-devices

[Matt Ranostay]

On Tuesday, 18 August 2026 at 05:29, Rodrigo Gobbi <rodrigo.gobbi.7@gmail.com> wrote:

> On 8/12/26 07:11, Matt Ranostay wrote:
> 
> >> >
> >> > diff --git a/Documentation/devicetree/bindings/iio/proximity/pulsedlight,lidar-lite-v2.yaml b/Documentation/devicetree/bindings/iio/proximity/pulsedlight,lidar-lite-v2.yaml
> >> > new file mode 100644
> >> > index 000000000000..e19c8d166b81
> >> > --- /dev/null
> >> > +++ b/Documentation/devicetree/bindings/iio/proximity/pulsedlight,lidar-lite-v2.yaml
> >> > @@ -0,0 +1,64 @@
> >> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> >> > +%YAML 1.2
> >> > +---
> >> > +$id: http://devicetree.org/schemas/iio/proximity/pulsedlight,lidar-lite-v2.yaml#
> >> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> >> > +
> >> > +title: Pulsedlight LIDAR-Lite v2 range-finding sensor
> >> > +
> >> > +maintainers:
> >> > +  - Matt Ranostay <mranostay@gmail.com>
> >
> > I really don't use my gmail address anymore. Would be ideal if it was changed matt@ranostay.sg
> > Other than that don't have any issues.
> >
> > Thanks,
> >
> > Matt
> 
> Thanks Matt, I will send a v6 fixing the e-mail. Since you're fine with it, would you
> mind sending a formal Reviewed-by/Acked-by?

Sure. Provide email change then LGTM.

Acked-by: Matt Ranostay <matt@ranostay.sg>

> 
> >
> >
> >> I'll need an Ack or Reviewed-by from Matt for this. If Matt either doesn't
> >> reply for a while, or isn't happy to take on this much fuller binding,
> >> is it something you'd consider putting yourself down for?
> >>
> >> Otherwise LGTM
> >>
> >> Thanks,
> >>
> >> Jonathan
> 
> I'm happy to be added as a second maintainer for this binding,
> (I can add myself at v6) but I'd rather defer to Matt as the
> primary one for now.
> Thanks!
> Rodrigo.
> 

[PATCH v5 2/2] dt-bindings: iio: proximity: document LIDAR-Lite v3 fallback compatible

[Rodrigo Gobbi]

PulsedLight was acquired by Garmin, who now sells the LIDAR-Lite v3.
It is pin-compatible with the v2, and the driver already matches it
directly: commit b257c1a45e99 ("iio: pulsedlight-lidar-lite-v2: add
lidar-lite-v3 property") added a "grmn,lidar-lite-v3" of_device_id
entry, so no driver changes are needed here.

Document it with "pulsedlight,lidar-lite-v2" as a fallback compatible.

Signed-off-by: Rodrigo Gobbi <rodrigo.gobbi.7@gmail.com>
---
 .../proximity/pulsedlight,lidar-lite-v2.yaml   | 18 ++++++++++++------
 1 file changed, 12 insertions(+), 6 deletions(-)

diff --git a/Documentation/devicetree/bindings/iio/proximity/pulsedlight,lidar-lite-v2.yaml b/Documentation/devicetree/bindings/iio/proximity/pulsedlight,lidar-lite-v2.yaml
index e19c8d166b81..baae9bf20a30 100644
--- a/Documentation/devicetree/bindings/iio/proximity/pulsedlight,lidar-lite-v2.yaml
+++ b/Documentation/devicetree/bindings/iio/proximity/pulsedlight,lidar-lite-v2.yaml
@@ -4,14 +4,14 @@
 $id: http://devicetree.org/schemas/iio/proximity/pulsedlight,lidar-lite-v2.yaml#
 $schema: http://devicetree.org/meta-schemas/core.yaml#
 
-title: Pulsedlight LIDAR-Lite v2 range-finding sensor
+title: Pulsedlight/Garmin LIDAR-Lite range-finding sensors
 
 maintainers:
   - Matt Ranostay <mranostay@gmail.com>
 
 description: |
-  This binding covers the I2C interface of the Pulsedlight LIDAR-Lite v2
-  laser rangefinder.
+  This binding covers the I2C interface of the Pulsedlight/Garmin
+  LIDAR-Lite v2 and v3 laser rangefinders.
 
   Besides I2C, the mode control pin can also trigger acquisitions and
   report the measured distance through a PWM signal, without using I2C
@@ -20,12 +20,18 @@ description: |
   remains the active interface, as a plain status output signalling
   when an acquisition has completed.
 
-  Datasheet:
+  Datasheets:
+    https://static.garmin.com/pumac/LIDAR_Lite_v3_Operation_Manual_and_Technical_Specifications.pdf
     https://github.com/PulsedLight3D/LIDAR-Lite-Documentation/blob/master/Docs/LIDAR-Lite-v2-Docs.pdf
 
 properties:
   compatible:
-    const: pulsedlight,lidar-lite-v2
+    oneOf:
+      - items:
+          - enum:
+              - grmn,lidar-lite-v3
+          - const: pulsedlight,lidar-lite-v2
+      - const: pulsedlight,lidar-lite-v2
 
   reg:
     maxItems: 1
@@ -56,7 +62,7 @@ examples:
         #address-cells = <1>;
         #size-cells = <0>;
         lidar@62 {
-            compatible = "pulsedlight,lidar-lite-v2";
+            compatible = "grmn,lidar-lite-v3", "pulsedlight,lidar-lite-v2";
             reg = <0x62>;
             vdd-supply = <&vdd_5v0>;
         };
-- 
2.48.1

Re: [PATCH v5 2/2] dt-bindings: iio: proximity: document LIDAR-Lite v3 fallback compatible

[Krzysztof Kozlowski]

On Mon, Aug 10, 2026 at 04:18:41PM -0300, Rodrigo Gobbi wrote:
> PulsedLight was acquired by Garmin, who now sells the LIDAR-Lite v3.
> It is pin-compatible with the v2, and the driver already matches it
> directly: commit b257c1a45e99 ("iio: pulsedlight-lidar-lite-v2: add
> lidar-lite-v3 property") added a "grmn,lidar-lite-v3" of_device_id
> entry, so no driver changes are needed here.

Drop ", so no driver..." - that is not really relevant.

Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>

Best regards,
Krzysztof

Re: [PATCH v5 0/2] iio: proximity: move LIDAR-Lite out of trivial-devices and add Garmin fallback

[Jonathan Cameron]

On Mon, 10 Aug 2026 16:18:39 -0300
Rodrigo Gobbi <rodrigo.gobbi.7@gmail.com> wrote:

> This series moves the LIDAR-Lite v2 binding out of trivial-devices
> into a dedicated schema, documenting the power-enable, power-supply
> and status-output interrupt properties that trivial-devices.yaml has
> no way to express.
> 
> It then adds the Garmin LIDAR-Lite v3 as a fallback compatible in a
> separate patch, since it is pin-compatible with the v2 and already
> matched by the driver, so no driver changes are needed.
> ---
Just enough stuff in here that I think a v6 tidying up (and hopefully
getting a tag from Matt) would be better than me trying to do
it as part of applying.

As such I've marked it changes requested in patchwork.

Jonathan

> Changelog:
> v5:
>   - split into two commits, one for moving lidar out of trivial and
>   one for adding a fallback compatible for LIDAR-Lite v3;
>   - minor changes at yaml like: title, description, adding irq prop;
>   - improve commit msgs for covering the vendor acquisition and PWM mode;
> v4: https://lore.kernel.org/all/20260714215433.41259-1-rodrigo.gobbi.7@gmail.com/
> v3: https://lore.kernel.org/all/20251102221643.9966-1-rodrigo.gobbi.7@gmail.com/
> v2: https://lore.kernel.org/all/20250801224112.135918-1-rodrigo.gobbi.7@gmail.com/
> v1: https://lore.kernel.org/all/20250701223341.36835-1-rodrigo.gobbi.7@gmail.com/
> ---
> Rodrigo Gobbi (2):
>   dt-bindings: iio: proximity: move LIDAR-Lite v2 out of trivial-devices
>   dt-bindings: iio: proximity: document LIDAR-Lite v3 fallback
>     compatible
> 
>  .../proximity/pulsedlight,lidar-lite-v2.yaml  | 70 +++++++++++++++++++
>  .../devicetree/bindings/trivial-devices.yaml  |  2 -
>  2 files changed, 70 insertions(+), 2 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/iio/proximity/pulsedlight,lidar-lite-v2.yaml
>