From: Liu Ying <victor.liu@nxp.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
andrzej.hajda@intel.com, narmstrong@baylibre.com,
robert.foss@linaro.org, jonas@kwiboo.se,
jernej.skrabec@gmail.com, airlied@linux.ie, daniel@ffwll.ch,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
lee.jones@linaro.org, mchehab@kernel.org,
marcel.ziswiler@toradex.com
Subject: Re: [PATCH v8 00/14] Add some DRM bridge drivers support for i.MX8qm/qxp SoCs
Date: Fri, 10 Jun 2022 10:27:36 +0800 [thread overview]
Message-ID: <c96522a1ebfe79d7a0cb8bf6311c59d92b015c5c.camel@nxp.com> (raw)
In-Reply-To: <YqG+Hxswo5ON1MX0@pendragon.ideasonboard.com>
Hi Laurent,
On Thu, 2022-06-09 at 12:32 +0300, Laurent Pinchart wrote:
> Hi Liu,
>
> On Thu, Jun 09, 2022 at 02:49:17PM +0800, Liu Ying wrote:
> > Hi,
> >
> > This is the v8 series to add some DRM bridge drivers support
> > for i.MX8qm/qxp SoCs.
> >
> > The bridges may chain one by one to form display pipes to support
> > LVDS displays. The relevant display controller is DPU embedded in
> > i.MX8qm/qxp SoCs.
> >
> > The DPU KMS driver can be found at:
> >
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatchwork.kernel.org%2Fproject%2Fdri-devel%2Flist%2F%3Fseries%3D629908%26state%3D%252A%26archive%3Dboth&data=05%7C01%7Cvictor.liu%40nxp.com%7C52bc453b59654345591f08da49faf477%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637903639438033239%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=ciw5SX%2FdUHu5z6tVpY383LBxkWmEoFu03ljhrkKsj%2FQ%3D&reserved=0
> >
> > This series supports the following display pipes:
> > 1) i.MX8qxp:
> > prefetch eng -> DPU -> pixel combiner -> pixel link ->
> > pixel link to DPI(PXL2DPI) -> LVDS display bridge(LDB)
> >
> > 2) i.MX8qm:
> > prefetch eng -> DPU -> pixel combiner -> pixel link -> LVDS display
> > bridge(LDB)
> >
> >
> > Patch 1/14 and 2/14 add bus formats used by pixel combiner.
> >
> > Patch 9/14 adds a helper for LDB bridge drivers.
> >
> > Patch 3/14 ~ 8/14 and 10/14 ~ 12/14 add drm bridge drivers and
> > dt-bindings support for the bridges.
> >
> > Patch 13/14 adds dt-binding for Control and Status Registers
> > module(a syscon
> > used by PXL2DPI and LDB), which references the PXL2DPI and LDB
> > schemas.
> >
> > Patch 14/14 updates MAINTAINERS.
> >
> >
> > I've tested this series with a koe,tx26d202vm0bwa dual link LVDS
> > panel and
> > a LVDS to HDMI bridge(with a downstream drm bridge driver).
> >
> > Marcel Ziswiler has tested v6 with two LVDS panels(single link
> > LT170410-2WHC
> > and dual link LP156WF1) on Toradex Colibri iMX8X.
> >
> >
> > Welcome comments, thanks.
>
> I'm not sure if this comment will be welcome, but what's the reason
> to
> handle the pixel combiner and pixel link (DPL) as bridges ? They seem
> very tightly couple with the display controller, wouldn't it be
> better
> to handle them in the display controller driver ?
i.MX8qxp display controller, pixel combiner and pixel link are
standalone IPs. i.MX8qxp reference manual has separate chapters for
them. Not sure if pixel combiner and/or pixel link will be used to
work with other display controllers in future SoCs. So, it looks
appropriate to take them as separate bridges.
Regards,
Liu Ying
prev parent reply other threads:[~2022-06-10 2:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 6:49 [PATCH v8 00/14] Add some DRM bridge drivers support for i.MX8qm/qxp SoCs Liu Ying
2022-06-09 6:49 ` [PATCH v8 01/14] media: uapi: Add some RGB bus formats for i.MX8qm/qxp pixel combiner Liu Ying
2022-06-09 6:49 ` [PATCH v8 02/14] media: docs: " Liu Ying
2022-06-09 6:49 ` [PATCH v8 03/14] dt-bindings: display: bridge: Add i.MX8qm/qxp pixel combiner binding Liu Ying
2022-06-09 8:24 ` Laurent Pinchart
2022-06-10 2:00 ` Liu Ying
2022-06-09 6:49 ` [PATCH v8 04/14] drm/bridge: imx: Add i.MX8qm/qxp pixel combiner support Liu Ying
2022-06-09 6:49 ` [PATCH v8 05/14] dt-bindings: display: bridge: Add i.MX8qm/qxp display pixel link binding Liu Ying
2022-06-09 6:49 ` [PATCH v8 06/14] drm/bridge: imx: Add i.MX8qm/qxp display pixel link support Liu Ying
2022-06-09 9:30 ` Laurent Pinchart
2022-06-10 2:09 ` Liu Ying
2022-06-10 12:40 ` Laurent Pinchart
2022-06-09 6:49 ` [PATCH v8 07/14] dt-bindings: display: bridge: Add i.MX8qxp pixel link to DPI binding Liu Ying
2022-06-09 6:49 ` [PATCH v8 08/14] drm/bridge: imx: Add i.MX8qxp pixel link to DPI support Liu Ying
2022-06-09 6:49 ` [PATCH v8 09/14] drm/bridge: imx: Add LDB driver helper support Liu Ying
2022-06-09 7:47 ` (EXT) " Alexander Stein
2022-06-10 3:01 ` Liu Ying
2022-06-13 14:12 ` (EXT) " Alexander Stein
2022-06-09 6:49 ` [PATCH v8 10/14] dt-bindings: display: bridge: Add i.MX8qm/qxp LVDS display bridge binding Liu Ying
2022-06-09 6:49 ` [PATCH v8 11/14] drm/bridge: imx: Add LDB support for i.MX8qxp Liu Ying
2022-06-09 6:49 ` [PATCH v8 12/14] drm/bridge: imx: Add LDB support for i.MX8qm Liu Ying
2022-06-09 6:49 ` [PATCH v8 13/14] dt-bindings: mfd: Add i.MX8qm/qxp Control and Status Registers module binding Liu Ying
2022-06-09 6:49 ` [PATCH v8 14/14] MAINTAINERS: add maintainer for DRM bridge drivers for i.MX SoCs Liu Ying
2022-06-09 9:32 ` [PATCH v8 00/14] Add some DRM bridge drivers support for i.MX8qm/qxp SoCs Laurent Pinchart
2022-06-10 2:27 ` Liu Ying [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=c96522a1ebfe79d7a0cb8bf6311c59d92b015c5c.camel@nxp.com \
--to=victor.liu@nxp.com \
--cc=airlied@linux.ie \
--cc=andrzej.hajda@intel.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@gmail.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=marcel.ziswiler@toradex.com \
--cc=mchehab@kernel.org \
--cc=narmstrong@baylibre.com \
--cc=robert.foss@linaro.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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).