From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
ML dri-devel <dri-devel@lists.freedesktop.org>,
linux-renesas-soc@vger.kernel.org,
devicetree <devicetree@vger.kernel.org>,
Tomi Valkeinen <tomi.valkeinen@ti.com>
Subject: Re: [PATCH v2 01/13] devicetree/bindings: display: Document common panel properties
Date: Tue, 11 Apr 2017 08:12:34 +0300 [thread overview]
Message-ID: <2098006.Rlj3CgHVZA@avalon> (raw)
In-Reply-To: <CACvgo52dydV5fpcDDPnFaRN32uxoeitvazwPpxOs4wOqg0=45A@mail.gmail.com>
Hi Emil,
On Sunday 09 Apr 2017 12:47:01 Emil Velikov wrote:
> Hi Laurent,
>
> Pardon for reviving this old thread. I've noticed a couple of things
> which might want some attention.
>
> On 19 November 2016 at 03:28, Laurent Pinchart wrote:
> > +
> > +- panel-timing: Most display panels are restricted to a single resolution
> > and + require specific display timings. The panel-timing subnode
> > expresses those + timings as specified in the timing subnode section of
> > the display timing + bindings defined in
> > + Documentation/devicetree/bindings/display/display-timing.txt.
>
> Cannot find such a file in linux-next. Perhaps you meant
> Documentation/devicetree/bindings/display/panel/display-timing.txt?
Oops. My bad, I'll fix that. Thank you for noticing it.
> Documentation/devicetree/bindings/display/panel/panel.txt includes a
> "rotation" property, which we might want to fold here.
I believe that panel.txt and panel-common.txt were added concurrently. We
should indeed merge the two.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2017-04-11 5:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-19 3:28 [PATCH v2 00/13] R-Car DU: Add support for LVDS mode selection Laurent Pinchart
2016-11-19 3:28 ` [PATCH v2 01/13] devicetree/bindings: display: Document common panel properties Laurent Pinchart
2016-11-21 16:48 ` Rob Herring
2016-11-22 9:36 ` Laurent Pinchart
2016-11-29 8:27 ` Laurent Pinchart
2016-11-29 15:14 ` Rob Herring
2016-11-29 18:23 ` Laurent Pinchart
2016-12-18 20:54 ` Laurent Pinchart
2016-12-19 15:38 ` Rob Herring
2016-12-19 16:54 ` Laurent Pinchart
2017-01-03 22:33 ` Rob Herring
[not found] ` <1479526093-7014-2-git-send-email-laurent.pinchart+renesas-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
2016-11-22 11:05 ` Thierry Reding
2016-11-22 13:14 ` Laurent Pinchart
2016-11-22 21:10 ` Rob Herring
2017-04-09 11:47 ` Emil Velikov
2017-04-11 5:12 ` Laurent Pinchart [this message]
2016-11-19 3:28 ` [PATCH v2 02/13] devicetree/bindings: display: Add bindings for LVDS panels Laurent Pinchart
[not found] ` <1479526093-7014-3-git-send-email-laurent.pinchart+renesas-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
2016-11-21 16:48 ` Rob Herring
2016-11-22 11:02 ` Thierry Reding
2016-11-22 13:21 ` Laurent Pinchart
[not found] ` <1479526093-7014-1-git-send-email-laurent.pinchart+renesas-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
2016-11-19 3:28 ` [PATCH v2 03/13] devicetree/bindings: display: Add bindings for two Mitsubishi panels Laurent Pinchart
2016-11-21 16:49 ` 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=2098006.Rlj3CgHVZA@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=tomi.valkeinen@ti.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).