From: Marek Vasut <marex@denx.de>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
dri-devel@lists.freedesktop.org
Cc: devicetree@vger.kernel.org, "Guido Günther" <agx@sigxcpu.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 3/7] dt-bindings: display: mxsfb: Add a bus-width endpoint property
Date: Wed, 7 Oct 2020 10:40:26 +0200 [thread overview]
Message-ID: <7b8df7af-5ca8-708b-4975-2fdf4280116f@denx.de> (raw)
In-Reply-To: <20201007012438.27970-4-laurent.pinchart@ideasonboard.com>
On 10/7/20 3:24 AM, Laurent Pinchart wrote:
[...]
> + bus-width:
> + enum: [16, 18, 24]
> + description: |
> + The output bus width. This value overrides the configuration
> + derived from the connected device (encoder or panel). It should
> + only be specified when PCB routing of the data signals require a
> + different bus width on the LCDIF and the connected device. For
> + instance, when a 18-bit RGB panel has its R[5:0], G[5:0] and
> + B[5:0] signals connected to LCD_DATA[7:2], LCD_DATA[15:10] and
> + LCD_DATA[23:18] instead of LCD_DATA[5:0], LCD_DATA[11:6] and
> + LCD_DATA[17:12], bus-width should be set to 24.
The iMX6 IPUv3 uses interface-pix-fmt which is a bit more flexible, but
I'm not sure whether it's the right way to go about this, see:
Documentation/devicetree/bindings/display/imx/fsl-imx-drm.txt
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-10-07 15:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 1:24 [PATCH v2 0/7] drm: mxsfb: Allow overriding bus width Laurent Pinchart
2020-10-07 1:24 ` [PATCH v2 1/7] dt-bindings: display: mxsfb: Convert binding to YAML Laurent Pinchart
2020-10-07 8:32 ` Marek Vasut
2020-10-07 8:43 ` Lucas Stach
2020-10-07 8:55 ` Marek Vasut
2020-10-07 13:33 ` Laurent Pinchart
2020-10-07 14:20 ` Marek Vasut
2020-10-07 16:00 ` Rob Herring
2020-10-07 16:02 ` Rob Herring
2020-10-09 23:52 ` Laurent Pinchart
2021-01-15 7:59 ` Martin Kepplinger
2021-01-15 22:25 ` Laurent Pinchart
2021-01-16 6:41 ` Martin Kepplinger
2020-10-07 1:24 ` [PATCH v2 2/7] dt-bindings: display: mxsfb: Add and fix compatible strings Laurent Pinchart
2020-10-07 8:35 ` Marek Vasut
2020-10-07 16:01 ` Rob Herring
2020-10-07 1:24 ` [PATCH v2 3/7] dt-bindings: display: mxsfb: Add a bus-width endpoint property Laurent Pinchart
2020-10-07 8:40 ` Marek Vasut [this message]
2020-10-09 23:58 ` Laurent Pinchart
2020-10-10 8:47 ` Marek Vasut
2020-10-13 2:06 ` Laurent Pinchart
2020-10-13 11:03 ` Marek Vasut
2020-10-07 16:03 ` Rob Herring
2020-10-07 1:24 ` [PATCH v2 4/7] ARM: dts: imx: Fix LCDIF compatible strings Laurent Pinchart
2020-10-07 1:24 ` [PATCH v2 5/7] arm64: dts: imx8mq: " Laurent Pinchart
2020-10-07 1:24 ` [PATCH v2 6/7] ARM: dts: imx: Remove unneeded LCDIF disp_axi clock Laurent Pinchart
2020-10-07 1:24 ` [PATCH v2 7/7] drm: mxsfb: Add support for the bus-width DT property Laurent Pinchart
2020-10-10 0:01 ` [PATCH v2 8/7] dt-bindings: display: mxsfb: Add compatible for i.MX8MM 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=7b8df7af-5ca8-708b-4975-2fdf4280116f@denx.de \
--to=marex@denx.de \
--cc=agx@sigxcpu.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@pengutronix.de \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robh+dt@kernel.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).