I know I've sent the previous version first as part of a longer list of patches, later individually, and now grouped together again. Sorry for the fuss, hope it's not too confusing. These three sensor bindings conversions go together as they all happen in a single patch, so I deemed it was easier to just group them. In v4 after finalizing the discussion with Laurent and Rob on how to handle of-graph endpoint, I have dropped them from mt9v111 and imx274. For imx214 as I have endpoint properties to document I have also documented 'endpoint' (not mandatory) and 'remote-endpoint' (mandatory). Hope I got the outcome of the discussion right. For imx214 I also took in Laurent's suggestion on how to document the 'data-lanes' supported values. Individual maintainers cc-ed per-patch. Thanks j Jacopo Mondi (3): dt-bindings: media: mt9v111: Convert to json-schema dt-bindings: media: imx274: Convert to json-schema dt-bindings: media: imx214: Convert to json-schema .../bindings/media/i2c/aptina,mt9v111.txt | 46 ------ .../bindings/media/i2c/aptina,mt9v111.yaml | 75 ++++++++++ .../devicetree/bindings/media/i2c/imx274.txt | 38 ----- .../bindings/media/i2c/sony,imx214.txt | 53 ------- .../bindings/media/i2c/sony,imx214.yaml | 137 ++++++++++++++++++ .../bindings/media/i2c/sony,imx274.yaml | 59 ++++++++ MAINTAINERS | 6 +- 7 files changed, 274 insertions(+), 140 deletions(-) delete mode 100644 Documentation/devicetree/bindings/media/i2c/aptina,mt9v111.txt create mode 100644 Documentation/devicetree/bindings/media/i2c/aptina,mt9v111.yaml delete mode 100644 Documentation/devicetree/bindings/media/i2c/imx274.txt delete mode 100644 Documentation/devicetree/bindings/media/i2c/sony,imx214.txt create mode 100644 Documentation/devicetree/bindings/media/i2c/sony,imx214.yaml create mode 100644 Documentation/devicetree/bindings/media/i2c/sony,imx274.yaml -- 2.28.0
