devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: dri-devel <dri-devel@lists.freedesktop.org>,
	devicetree@vger.kernel.org,
	Oleksandr Suvorov <oleksandr.suvorov@toradex.com>,
	Maxime Ripard <mripard@kernel.org>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	Peter Ujfalusi <peter.ujfalusi@ti.com>,
	Steffen Trumtrar <s.trumtrar@pengutronix.de>,
	Philipp Zabel <p.zabel@pengutronix.de>
Subject: Re: [PATCH v3 4/5] dt-bindings: display: add data-mapping to panel-dpi
Date: Tue, 18 Feb 2020 21:02:00 -0600	[thread overview]
Message-ID: <20200219030200.GA9263@bogus> (raw)
In-Reply-To: <20200218221638.GA27927@ravnborg.org>

On Tue, Feb 18, 2020 at 11:16:38PM +0100, Sam Ravnborg wrote:
> On Tue, Feb 18, 2020 at 02:13:45PM -0600, Rob Herring wrote:
> > On Sun, Feb 16, 2020 at 12:15 PM Sam Ravnborg <sam@ravnborg.org> wrote:
> > >
> > > Add data-mapping property that can be used to specify
> > > the media format used for the connection betwwen the
> > > display controller (connector) and the panel.
> > > Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
> > 
> > Missing blank line.
> > 
> > > ---
> > >  .../devicetree/bindings/display/panel/panel-dpi.yaml | 12 +++++++++++-
> > >  1 file changed, 11 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/Documentation/devicetree/bindings/display/panel/panel-dpi.yaml b/Documentation/devicetree/bindings/display/panel/panel-dpi.yaml
> > > index 40079fc24a63..6a03d2449701 100644
> > > --- a/Documentation/devicetree/bindings/display/panel/panel-dpi.yaml
> > > +++ b/Documentation/devicetree/bindings/display/panel/panel-dpi.yaml
> > > @@ -21,6 +21,16 @@ properties:
> > >        - {}
> > >        - const: panel-dpi
> > >
> > > +  data-mapping:
> > > +    enum:
> > > +      - rgb24
> > > +      - rgb565
> > > +      - bgr666
> > > +      - lvds666
> > 
> > Doesn't lvds666 come from i.MX IPU which as I remember has built-in
> > LVDS block? I'd think this format would be implicit when using the
> > LVDS block and panel. It doesn't seem this is actually used anywhere
> > either.
> I must admit that I just copied this list from Oleksandrs original
> patch. The MEDIA type it identifies(MEDIA_BUS_FMT_RGB666_1X24_CPADHI) looks special.
> I will drop lvds666 while applying, unless I get other feedback.
> (Note: travelling, earliest in the weekend)

Okay, with that:

Reviewed-by: Rob Herring <robh@kernel.org>

> 
> Btw. anyway I can add data-mapping to panel-common - and then list the
> allowed enum values in each binding?

That would be good. It should be defined explicitly that it's a single 
string as that's implicit currently.
 
Rob

  reply	other threads:[~2020-02-19  3:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-16 18:15 [PATCH v3 0/5] dt-bindings: convert timing + panel-dpi to DT schema Sam Ravnborg
2020-02-16 18:15 ` [PATCH v3 1/5] dt-bindings: display: add panel-timing.yaml Sam Ravnborg
2020-02-16 18:15 ` [PATCH v3 2/5] dt-bindings: display: convert display-timings to DT schema Sam Ravnborg
2020-03-03 18:46   ` Laurent Pinchart
2020-02-16 18:15 ` [PATCH v3 3/5] dt-bindings: display: convert panel-dpi " Sam Ravnborg
2020-02-18 20:01   ` Rob Herring
2020-03-03 19:00   ` Laurent Pinchart
2020-02-16 18:15 ` [PATCH v3 4/5] dt-bindings: display: add data-mapping to panel-dpi Sam Ravnborg
2020-02-18 20:13   ` Rob Herring
2020-02-18 22:16     ` Sam Ravnborg
2020-02-19  3:02       ` Rob Herring [this message]
2020-03-03 18:55       ` Laurent Pinchart
2020-02-16 18:15 ` [RFC PATCH v3 5/5] drm/panel: simple: add panel-dpi support Sam Ravnborg
2020-02-17 12:13   ` Maxime Ripard
2020-02-17 13:29   ` Oleksandr Suvorov
2020-03-03 19:00   ` Laurent Pinchart
2020-02-29 18:13 ` [PATCH v3 0/5] dt-bindings: convert timing + panel-dpi to DT schema Sam Ravnborg
2020-03-03 18:48   ` Laurent Pinchart

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=20200219030200.GA9263@bogus \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=mripard@kernel.org \
    --cc=oleksandr.suvorov@toradex.com \
    --cc=p.zabel@pengutronix.de \
    --cc=peter.ujfalusi@ti.com \
    --cc=s.trumtrar@pengutronix.de \
    --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).