Re: [PATCH] dt-bindings: iio: adc: add AD7816/AD7817/AD7818 binding

[sashiko-bot@kernel.org]

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] GPIO properties described as optional are enforced as strictly required in the schema.
--

commit 5e87ac2e842cf4989944934ecd916083ea3da1f7
Author: Hungyu Lin <dennylin0707@gmail.com>

dt-bindings: iio: adc: add AD7816/AD7817/AD7818 binding

Add Device Tree binding documentation for the Analog Devices
AD7816, AD7817 and AD7818 SPI ADC devices.

> diff --git a/Documentation/devicetree/bindings/iio/adc/adi,ad7816.yaml b/Documentation/devicetree/bindings/iio/adc/adi,ad7816.yaml
> new file mode 100644
> index 0000000000000..490e5338d7b2e
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/adc/adi,ad7816.yaml

[ ... ]

> +required:
> +  - compatible
> +  - reg
> +  - rdwr-gpios
> +  - convert-gpios

The commit message states that the devices "may use control GPIOs for RD/WR
and CONVST", which implies they are optional. 

Are rdwr-gpios and convert-gpios strictly required for operation? If they can
be left unconnected or hardwired depending on the board's hardware design,
enforcing them in the global required block will cause valid device trees to
fail validation.

> +
> +allOf:
> +  - $ref: /schemas/spi/spi-peripheral-props.yaml#
> +
> +  - if:
> +      properties:
> +        compatible:
> +          contains:
> +            enum:
> +              - adi,ad7816
> +              - adi,ad7817
> +    then:
> +      required:
> +        - busy-gpios

Does the same apply to busy-gpios? The commit message mentions BUSY is
optional depending on the device variant, but this block enforces it as
mandatory for the AD7816 and AD7817 variants.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260508202005.76278-1-dennylin0707@gmail.com?part=1