Re: [RESEND PATCH v4 3/3] dt-bindings: drm: bridge: adi, adv7511.txt: convert to yaml

Hi Geert,

On Fri, Jun 18, 2021 at 09:55:38AM +0200, Geert Uytterhoeven wrote:

On Tue, Jun 15, 2021 at 3:15 PM Ricardo Cañuelo wrote:

quoted

Convert the ADV7511/11w/13/33/35 DT bindings to json-schema. The
original binding has been split into two files: adi,adv7511.yaml for
ADV7511/11W/13 and adi,adv7533.yaml for ADV7533/35.

Signed-off-by: Ricardo Cañuelo <redacted>
Reviewed-by: Rob Herring <robh@kernel.org>
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>

Thanks for your patch, which is now commit cfe34bb7a770c5d8
("dt-bindings: drm: bridge: adi,adv7511.txt: convert to yaml")
in robh/for-next.

quoted

--- /dev/null
+++ b/Documentation/devicetree/bindings/display/bridge/adi,adv7511.yaml

quoted

+required:
+  - compatible
+  - reg
+  - ports
+  - adi,input-depth
+  - adi,input-colorspace
+  - adi,input-clock
+  - avdd-supply
+  - dvdd-supply
+  - pvdd-supply
+  - dvdd-3v-supply
+  - bgvdd-supply

This causes lots of failures like:

    arm/boot/dts/r8a7743-iwg20d-q7-dbcm-ca.dt.yaml: hdmi@39:
'avdd-supply' is a required property

Should all supplies be required?
Looking at the driver, missing supplies are automatically replaced by
dummy regulators by the regulator framework.

Generally speaking, I like DT bindings to be descriptive of the
hardware, and thus require power supplies that are needed for the device
to function, even if they are fixed supplies.

This being said, I think there's also room to group some power supplies
together in the bindings, when they are not meant by the device to be
controlled separately. In this specific case, we also need to take into
account that the adv7511 and adv7533 have different supplies.

-- 
Regards,

Laurent Pinchart

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel