This series moves the Lidar v2 binding from trivial to a dedicated place.
It also adds the v3, which was not described yet, in the same place since
it's the same hardware and it is already supported by the driver.
---
Hi, all,
Very few changes in this v3. At the v2 link, there was a discussion about
the PWM output pin and the current support of that. It was suggested to
not add that pin here, at least for now.
Tks and regards.

Changelog:
v3: split things in a patchset
    replace power-gpios to powerdown-gpios
    user proper lidar node name
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/#t
---
Rodrigo Gobbi (2):
  dt-bindings: iio: proximity: Remove Lidar-lite-v2 from trivial
  dt-bindings: iio: proximity: Add Lidar-lite-v2 and v3

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

-- 
2.48.1

On 02/11/2025 23:10, Rodrigo Gobbi wrote:
> This series moves the Lidar v2 binding from trivial to a dedicated place.
> It also adds the v3, which was not described yet, in the same place since
> it's the same hardware and it is already supported by the driver.
> ---
> Hi, all,
> Very few changes in this v3. At the v2 link, there was a discussion about
> the PWM output pin and the current support of that. It was suggested to
> not add that pin here, at least for now.
> Tks and regards.
> 
> Changelog:
> v3: split things in a patchset

Hm? Why. That's non-bisectable now



Best regards,
Krzysztof