From: Sam Ravnborg <sam@ravnborg.org>
To: Rob Herring <robh@kernel.org>
Cc: dri-devel <dri-devel@lists.freedesktop.org>,
devicetree@vger.kernel.org, Maxime Ripard <mripard@kernel.org>,
Chen-Yu Tsai <wens@csie.org>,
Thierry Reding <thierry.reding@gmail.com>
Subject: Re: [PATCH] dt-bindings: display: Convert a bunch of panels to DT schema
Date: Mon, 9 Dec 2019 19:00:35 +0100 [thread overview]
Message-ID: <20191209180035.GA14817@ravnborg.org> (raw)
In-Reply-To: <CAL_JsqLNSF3j9q49SVTpg=742dgt-60BRhXUxEVUXyYtroAqOQ@mail.gmail.com>
Hi Rob.
>
> Yes. The issue would be enforcing the big disclaimer of "Do not add
> your panel here unless it has a single power rail." (And anything else
> we think of). Between a single line add vs. a whole new doc, you know
> what people will pick. I guess panels could still be moved out of the
> common doc later on. We'd also have to be fighting off the "let me add
> just one new property for my panel".
If the panel cannot be supported by the panel-simple driver then
this is a good sign that it does not belong in the bindings file.
Or something like this.
I do not see it as a 1:1 for all panels but I guess most panels
supported by panel-simple would go in a single bindings file.
> You did. I'd like to hear Thierry's thoughts on this before going down
> this path.
Seconded, Thierry?
Sam
prev parent reply other threads:[~2019-12-09 18:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 23:13 [PATCH] dt-bindings: display: Convert a bunch of panels to DT schema Rob Herring
2019-11-30 19:43 ` Sam Ravnborg
2019-12-02 14:38 ` Rob Herring
2019-12-04 20:14 ` Sam Ravnborg
2019-12-09 17:39 ` Rob Herring
2019-12-09 18:00 ` Sam Ravnborg [this message]
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=20191209180035.GA14817@ravnborg.org \
--to=sam@ravnborg.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=mripard@kernel.org \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=wens@csie.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).