From: Linus Walleij <linus.walleij@linaro.org>
To: Rob Herring <robh@kernel.org>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Sam Ravnborg <sam@ravnborg.org>,
"open list:DRM PANEL DRIVERS" <dri-devel@lists.freedesktop.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>
Subject: Re: [PATCH 1/3 v4] drm/panel: Add generic DSI panel YAML bindings
Date: Wed, 30 Oct 2019 14:50:20 +0100 [thread overview]
Message-ID: <CACRpkdZ67mC9m6inJSfbS0NqeThfJ0tUJQTP5stX3Kzw+zhEyQ@mail.gmail.com> (raw)
In-Reply-To: <20191025192054.GA7415@bogus>
On Fri, Oct 25, 2019 at 9:20 PM Rob Herring <robh@kernel.org> wrote:
> [Me]
> > + dsi-controller@55aa55aa {
> > + compatible = "acme,foo";
>
> Eventually, I want to start reporting if compatible strings aren't
> documented (i.e. matched to a schema). This will break then...
OK I drop this.
> > + reg = <0x55aa55aa>;
>
> This will fail because a size cell is expected.
Do you mean it will fail the day we actually check reg properties to
be properly formed under the circumstances?
Because:
HOSTLD scripts/dtc/dtc
CHKDT Documentation/devicetree/bindings/display/panel/sony,acx424akp.yaml
CHKDT Documentation/devicetree/bindings/display/dsi-controller.yaml
SCHEMA Documentation/devicetree/bindings/processed-schema.yaml
(...)
It passes just fine.
I get a bit nervous since the schema is all about being strict about
stuff so I get the feeling that "should have failed".
Yours,
Linus Walleij
next prev parent reply other threads:[~2019-10-30 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 11:43 [PATCH 1/3 v4] drm/panel: Add generic DSI panel YAML bindings Linus Walleij
2019-10-24 11:43 ` [PATCH 2/3 v4] drm/panel: Add DT bindings for Sony ACX424AKP Linus Walleij
2019-10-25 19:25 ` Rob Herring
2019-10-30 16:37 ` Linus Walleij
2019-10-30 19:41 ` Rob Herring
2019-10-25 19:20 ` [PATCH 1/3 v4] drm/panel: Add generic DSI panel YAML bindings Rob Herring
2019-10-30 13:50 ` Linus Walleij [this message]
2019-10-30 19:45 ` Rob Herring
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=CACRpkdZ67mC9m6inJSfbS0NqeThfJ0tUJQTP5stX3Kzw+zhEyQ@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=robh@kernel.org \
--cc=sam@ravnborg.org \
--cc=thierry.reding@gmail.com \
/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).