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

[sashiko-bot@kernel.org]

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Making `vdd-supply` strictly required breaks schema validation for all existing valid device trees.
--

--- Patch [1]: [PATCH v6 1/2] dt-bindings: iio: proximity: move LIDAR-Lite v2 out of trivial-devices ---
commit a1ef458d9c0cdfc9e29367cfdc33a99254dccf2e
Author: Rodrigo Gobbi <rodrigo.gobbi.7@gmail.com>

dt-bindings: iio: proximity: move LIDAR-Lite v2 out of trivial-devices

The PulsedLight LIDAR-Lite v2 is moved out of trivial-devices into a dedicated
binding file to document its power-enable, power-supply, and interrupt
properties.

> 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 0000000000000..491960bb3a0e9
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/proximity/pulsedlight,lidar-lite-v2.yaml

[ ... ]

> +required:
> +  - compatible
> +  - reg
> +  - vdd-supply

[Severity: Low]
Does making vdd-supply strictly required break schema validation for existing
device trees?

Since this device was previously validated against trivial-devices.yaml where
this supply was not defined, running make dtbs_check with an older, valid
device tree containing pulsedlight,lidar-lite-v2 but lacking vdd-supply
will fail.

Should this property be optional to maintain backward compatibility with older
device trees?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260819205751.166030-1-rodrigo.gobbi.7@gmail.com?part=1