On Fri, Jul 17, 2020 at 03:28:51PM +0200, Jacopo Mondi wrote: > The ov5640 driver supports both a parallel data interface and a > CSI-2 serial data interface. > > Depending on which interface is in use, the required endpoint > properties are different. In order to be able to validate if a > device node is compliant with the dt-schema bindings, start by > making the bus-type a mandatory property, and add it to all the > existing users of ov5640 in mainline DTS. You can't really make a property required on an existing binding. That breaks compatibility. Are all the users of the below boards okay with that? There should be a default defined if 'bus-type' is not present. > > On top of this, endpoint properties validation will be implemented, > conditionally to the reported bus type. > > Signed-off-by: Jacopo Mondi <jacopo+renesas@xxxxxxxxxx> > --- > Documentation/devicetree/bindings/media/i2c/ov5640.yaml | 6 ++++++ > arch/arm/boot/dts/dra72-evm-common.dtsi | 1 + > arch/arm/boot/dts/dra76-evm.dts | 1 + > arch/arm/boot/dts/imx6-logicpd-baseboard.dtsi | 1 + > arch/arm/boot/dts/imx6qdl-icore.dtsi | 1 + > arch/arm/boot/dts/imx6qdl-sabrelite.dtsi | 1 + > arch/arm/boot/dts/imx6qdl-sabresd.dtsi | 1 + > arch/arm/boot/dts/stm32mp157c-ev1.dts | 1 + > arch/arm64/boot/dts/allwinner/sun50i-a64-amarula-relic.dts | 1 + > arch/arm64/boot/dts/allwinner/sun50i-a64-pinetab.dts | 1 + > arch/arm64/boot/dts/qcom/apq8016-sbc.dtsi | 1 + > arch/arm64/boot/dts/ti/k3-am654-base-board.dts | 1 + > 12 files changed, 17 insertions(+)
