From: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
Cc: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH v3 0/3] dtc: checks for phandle with arg properties
Date: Fri, 1 Sep 2017 13:53:00 -0500 [thread overview]
Message-ID: <20170901185303.24770-1-robh@kernel.org> (raw)
David,
Here's a new version of checks for phandle with arg style properties. This
checks interrupt and gpio bindings and other common bindings which follow
the same phandle plus args pattern.
This generates ~200 warnings building the ARM dts files in the kernel.
Rob
Rob Herring (3):
checks: add phandle with arg property checks
checks: add gpio binding properties check
checks: add interrupts property check
checks.c | 280 ++++++++++++++++++++++++++++++++++++++++++
dtc.h | 1 +
livetree.c | 6 +
tests/bad-gpio.dts | 13 ++
tests/bad-interrupt-cells.dts | 12 ++
tests/bad-phandle-cells.dts | 11 ++
tests/run_tests.sh | 4 +
7 files changed, 327 insertions(+)
create mode 100644 tests/bad-gpio.dts
create mode 100644 tests/bad-interrupt-cells.dts
create mode 100644 tests/bad-phandle-cells.dts
--
2.11.0
next reply other threads:[~2017-09-01 18:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 18:53 Rob Herring [this message]
[not found] ` <20170901185303.24770-1-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-09-01 18:53 ` [PATCH v3 1/3] checks: add phandle with arg property checks Rob Herring
2017-09-01 18:53 ` [PATCH v3 2/3] checks: add gpio binding properties check Rob Herring
2017-09-01 18:53 ` [PATCH v3 3/3] checks: add interrupts property check Rob Herring
2017-09-20 22:13 ` [PATCH v3 0/3] dtc: checks for phandle with arg properties Rob Herring
[not found] ` <CAL_JsqLuO24jUO3D_9ROT+tOS6iQEyPGgT8tts7C3bwXPWwskg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-09-22 11:01 ` David Gibson
2017-09-22 11:24 ` David Gibson
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=20170901185303.24770-1-robh@kernel.org \
--to=robh-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.