Convert the ov722x bindings to json-schema and add endpoint properties and bus-type. Compared to v3 in 1/3 I have not documented 'endpoint' Then 2/3 introduces the 'bus-type' endpoint properties, so I had to document 'endpoint' and list 'remote-endpoint' as required (which makes me think I could have kept it in 1/3, but for sake of consistency...) 3/3 adds endpoint properties, whose presence is conditional to the specified bus-type. Thanks j Jacopo Mondi (3): dt-bindings: media: ov772x: Convert to json-schema dt-bindings: media: ov772x: Make bus-type mandatory dt-bindings: media: ov772x: Document endpoint props .../devicetree/bindings/media/i2c/ov772x.txt | 40 ----- .../bindings/media/i2c/ovti,ov772x.yaml | 138 ++++++++++++++++++ MAINTAINERS | 2 +- 3 files changed, 139 insertions(+), 41 deletions(-) delete mode 100644 Documentation/devicetree/bindings/media/i2c/ov772x.txt create mode 100644 Documentation/devicetree/bindings/media/i2c/ovti,ov772x.yaml -- 2.28.0
