From: "Ricardo Cañuelo" <ricardo.canuelo@collabora.com>
To: robh@kernel.org
Cc: kernel@collabora.com, enric.balletbo@collabora.com,
bleung@chromium.org, groeck@chromium.org, sjg@chromium.org,
dianders@chromium.org, devicetree@vger.kernel.org
Subject: [PATCH 0/3] Fix checker warnings related to cros-ec binding
Date: Mon, 5 Oct 2020 09:13:59 +0200 [thread overview]
Message-ID: <20201005071403.17450-1-ricardo.canuelo@collabora.com> (raw)
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
next reply other threads:[~2020-10-05 7:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 7:13 Ricardo Cañuelo [this message]
2020-10-05 7:14 ` [PATCH 1/3] dt-bindings: i2c: convert i2c-cros-ec-tunnel to json-schema Ricardo Cañuelo
2020-10-05 8:52 ` Enric Balletbo i Serra
2020-10-05 9:18 ` Ricardo Cañuelo
2020-10-05 9:27 ` Enric Balletbo i Serra
2020-10-05 14:04 ` Rob Herring
2020-10-05 7:14 ` [PATCH 2/3] dt-bindings: input: convert cros-ec-keyb " Ricardo Cañuelo
2020-10-05 9:03 ` Enric Balletbo i Serra
2020-10-05 9:35 ` Ricardo Cañuelo
2020-10-05 7:14 ` [PATCH 3/3] dt-bindings: mfd: google,cros-ec: add missing properties Ricardo Cañuelo
2020-10-05 9:23 ` Enric Balletbo i Serra
2020-10-05 9:48 ` Ricardo Cañuelo
2020-10-05 15:37 ` Rob Herring
2020-10-05 15:48 ` Enric Balletbo i Serra
2020-10-06 6:13 ` Ricardo Cañuelo
2020-10-06 11:28 ` Guenter Roeck
2020-10-06 13:07 ` Ricardo Cañuelo
2020-10-06 21:35 ` Rob Herring
2020-10-07 6:31 ` Ricardo Cañuelo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201005071403.17450-1-ricardo.canuelo@collabora.com \
--to=ricardo.canuelo@collabora.com \
--cc=bleung@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=kernel@collabora.com \
--cc=robh@kernel.org \
--cc=sjg@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).