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

[Krzysztof Kozlowski <krzk@kernel.org>]

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