This series fixes a bunch of warnings related to the google,cros-ec binding, originally reported by Rob Herring. The patches involve adding missing subnode definitions in the google,cros-ec binding and the conversion of two existing bindings to json-schema. All the related warnings should be fixed after applying the patches, except for a couple of warnings in the device trees of Qualcomm's Trogdor and Cheza chromebooks. They define a pdupdate subnode inside cros-ec that has no binding, the development of drivers and support for these chromebooks is ongoing and not completely upstreamed yet. Bindings tested with: make dt_binding_check ARCH=<arch> DT_SCHEMA_FILES=... make dtbs_check ARCH=<arch> DT_SCHEMA_FILES=... for <arch> = arm and arm64. Kind regards, Ricardo Ricardo Cañuelo (3): dt-bindings: i2c: convert i2c-cros-ec-tunnel to json-schema dt-bindings: input: convert cros-ec-keyb to json-schema dt-bindings: mfd: google,cros-ec: add missing properties .../i2c/google,cros-ec-i2c-tunnel.yaml | 56 +++++++++++ .../bindings/i2c/i2c-cros-ec-tunnel.txt | 39 -------- .../bindings/input/cros-ec-keyb.txt | 72 --------------- .../bindings/input/google,cros-ec-keyb.yaml | 92 +++++++++++++++++++ .../bindings/mfd/google,cros-ec.yaml | 40 ++++++++ 5 files changed, 188 insertions(+), 111 deletions(-) create mode 100644 Documentation/devicetree/bindings/i2c/google,cros-ec-i2c-tunnel.yaml delete mode 100644 Documentation/devicetree/bindings/i2c/i2c-cros-ec-tunnel.txt delete mode 100644 Documentation/devicetree/bindings/input/cros-ec-keyb.txt create mode 100644 Documentation/devicetree/bindings/input/google,cros-ec-keyb.yaml -- 2.18.0
