dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Stefan Agner <stefan@agner.ch>, Peter Rosin <peda@axentia.se>
Cc: Marek Vasut <marex@denx.de>, David Airlie <airlied@linux.ie>,
	Ahmad Fatoum <a.fatoum@pengutronix.de>,
	dri-devel@lists.freedesktop.org, kernel@pengutronix.de
Subject: Re: [PATCH 0/3] drm/mxsfb: support swapped RGB lanes
Date: Wed, 2 Jan 2019 22:37:57 +0100	[thread overview]
Message-ID: <20190102213757.GA28180@ravnborg.org> (raw)
In-Reply-To: <719c261f00bef5b805bf74b53e7d6cc5@agner.ch>

Hi Ahmad.

On Wed, Jan 02, 2019 at 10:05:31PM +0100, Stefan Agner wrote:
> On 02.01.2019 18:02, Ahmad Fatoum wrote:
> > Hello,
> > 
> > I got a board with the RED[0:7]/BLUE[0:7] lanes originating from the
> > LCDIF swapped and would like to describe this in the device tree:
> > 
> > This first patch extends the mxsfb driver to support
> > following bus formats:
> > 	MEDIA_BUS_FMT_BGR888_1X24
> > 	MEDIA_BUS_FMT_RBG888_1X24
> > 	MEDIA_BUS_FMT_GBR888_1X24
> > 
> > The latter two patches add a new interface-pix-fmt property
> > (named so because fsl,imx-parallel-display has one),
> > which allows a device tree to override the bus format to account
> > for swapped signal lanes.
> > 
> > Thoughts?
I have not seen the original mail, so a reply to this mail.
The problem with the RED/BLUE lines swapped is something I
have encountered while working with DRM support for Atmel at91sam9263 too.

The solution selected is to extend the endpoint with
a new optional property:

- wiring: Wiring of data lines to display.
  "straight" - normal wiring.
  "red-blue-reversed" - red and blue lines reversed.

(media/video-interfaces.txt)


The DT node looks like this:

               port@0 {
                        reg = <0>;
                        #address-cells = <1>;
                        #size-cells = <0>;
                        lcdc_panel_output: endpoint@0 {
                                reg = <0>;
                                wiring = "red-blue-reversed";
                                remote-endpoint = <&panel_input>;
                        };
                };

This allows us to specify the swapping in the endpoint and
not in the panel.
So we can use the same panel, with the same bus_format, in several
designs some with red-blue swapped (reversed), and some not.

This above is inspired by some earlier thread on dri-devel.
I recall Peter Rosin was one of the main source of inspiration.

Patches I refer to are not yet posted, this is work-in-progess.
They need more polishing and testing before they are dri-devel ready.

	Sam
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2019-01-02 21:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-02 17:02 [PATCH 0/3] drm/mxsfb: support swapped RGB lanes Ahmad Fatoum
2019-01-02 17:02 ` [PATCH 1/3] drm/mxsfb: use bus_format to determine pixel RGB component order Ahmad Fatoum
2019-01-02 17:14   ` Ahmad Fatoum
2019-01-02 17:02 ` [PATCH 2/3] drm/mxsfb: implement interface-pix-fmt of_property to override bus format Ahmad Fatoum
2019-01-02 17:02 ` [PATCH 3/3] dt-bindings: mxsfb: document new interface-pix-fmt property Ahmad Fatoum
2019-01-02 21:05 ` [PATCH 0/3] drm/mxsfb: support swapped RGB lanes Stefan Agner
2019-01-02 21:37   ` Sam Ravnborg [this message]
2019-01-07 17:35     ` Ahmad Fatoum
2019-01-07 18:04       ` Sam Ravnborg
2019-03-27 14:26         ` Ahmad Fatoum
2019-01-03  9:59   ` Ahmad Fatoum
2019-03-27 14:30   ` Ahmad Fatoum

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=20190102213757.GA28180@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=a.fatoum@pengutronix.de \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kernel@pengutronix.de \
    --cc=marex@denx.de \
    --cc=peda@axentia.se \
    --cc=stefan@agner.ch \
    /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