From: Francesco Dolcini <francesco@dolcini.it>
To: Liu Ying <victor.liu@nxp.com>
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-phy@lists.infradead.org,
p.zabel@pengutronix.de, airlied@gmail.com, simona@ffwll.ch,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, tglx@linutronix.de,
vkoul@kernel.org, kishon@kernel.org, Frank.Li@nxp.com,
lumag@kernel.org, aisheng.dong@nxp.com, agx@sigxcpu.org,
u.kleine-koenig@baylibre.com, francesco@dolcini.it,
dmitry.baryshkov@linaro.org
Subject: Re: [PATCH v9 00/19] Add Freescale i.MX8qxp Display Controller support
Date: Tue, 14 Jul 2026 21:36:27 +0200 [thread overview]
Message-ID: <20260714193627.GA9616@francesco-nb> (raw)
In-Reply-To: <20250414035028.1561475-1-victor.liu@nxp.com>
Hello Liu,
On Mon, Apr 14, 2025 at 11:50:09AM +0800, Liu Ying wrote:
> Hi,
>
> This patch series aims to add Freescale i.MX8qxp Display Controller support.
>
> The controller is comprised of three main components that include a blit
> engine for 2D graphics accelerations, display controller for display output
> processing, as well as a command sequencer.
...
>
> To follow up i.MX8qxp TRM, I changed the controller name to "Display Controller"
> instead of the previous "DPU". "DPU" is only mentioned in the SoC block
> diagram and represents the whole display subsystem which includes the display
> controller and prefech engines, etc.
>
> With an additional patch[1] for simple-pm-bus.c, this series facilitates
> testing a LVDS panel on i.MX8qxp MEK.
>
> Please do NOT merge patch 14-19. They are only used to facilitate testing
> the LVDS panel.
What's the plan to conclude this work? What's the latest status?
I am looking forward to have a way to use the i.MX8QXP display with
mainline, but to my understanding some required changes on the SOC dtsi
are not merged.
Can you help?
Thanks,
Francesco
prev parent reply other threads:[~2026-07-14 19:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 3:50 [PATCH v9 00/19] Add Freescale i.MX8qxp Display Controller support Liu Ying
2025-04-14 3:50 ` [PATCH v9 01/19] dt-bindings: display: imx: Add i.MX8qxp Display Controller processing units Liu Ying
2025-04-14 3:50 ` [PATCH v9 02/19] dt-bindings: display: imx: Add i.MX8qxp Display Controller blit engine Liu Ying
2025-04-14 3:50 ` [PATCH v9 03/19] dt-bindings: display: imx: Add i.MX8qxp Display Controller display engine Liu Ying
2025-04-14 3:50 ` [PATCH v9 04/19] dt-bindings: display: imx: Add i.MX8qxp Display Controller pixel engine Liu Ying
2025-04-14 3:50 ` [PATCH v9 05/19] dt-bindings: display: imx: Add i.MX8qxp Display Controller AXI performance counter Liu Ying
2025-04-14 3:50 ` [PATCH v9 06/19] dt-bindings: display: imx: Add i.MX8qxp Display Controller command sequencer Liu Ying
2025-04-14 3:50 ` [PATCH v9 07/19] dt-bindings: interrupt-controller: Add i.MX8qxp Display Controller interrupt controller Liu Ying
2025-04-14 3:50 ` [PATCH v9 08/19] dt-bindings: display: imx: Add i.MX8qxp Display Controller Liu Ying
2025-04-14 3:50 ` [PATCH v9 09/19] drm/imx: Add i.MX8qxp Display Controller display engine Liu Ying
2025-04-14 3:50 ` [PATCH v9 10/19] drm/imx: Add i.MX8qxp Display Controller pixel engine Liu Ying
2025-04-14 3:50 ` [PATCH v9 11/19] drm/imx: Add i.MX8qxp Display Controller interrupt controller Liu Ying
2025-04-14 3:50 ` [PATCH v9 12/19] drm/imx: Add i.MX8qxp Display Controller KMS Liu Ying
2025-04-14 3:50 ` [PATCH v9 13/19] MAINTAINERS: Add maintainer for i.MX8qxp Display Controller Liu Ying
2025-04-14 3:50 ` [DO NOT MERGE PATCH v9 14/19] dt-bindings: phy: mixel, mipi-dsi-phy: Allow assigned-clock* properties Liu Ying
2025-04-14 3:50 ` [DO NOT MERGE PATCH v9 15/19] dt-bindings: firmware: imx: Add SCU controlled display pixel link nodes Liu Ying
2025-04-14 3:50 ` [DO NOT MERGE PATCH v9 16/19] arm64: dts: imx8qxp: Add display controller subsystem Liu Ying
2025-04-14 3:50 ` [DO NOT MERGE PATCH v9 17/19] arm64: dts: imx8qxp: Add MIPI-LVDS combo subsystems Liu Ying
2025-04-14 3:50 ` [DO NOT MERGE PATCH v9 18/19] arm64: dts: imx8qxp-mek: Enable display controller Liu Ying
2025-04-14 3:50 ` [DO NOT MERGE PATCH v9 19/19] arm64: dts: imx8qxp-mek: Add MX8-DLVDS-LCD1 display module support Liu Ying
2025-05-07 7:19 ` [PATCH v9 00/19] Add Freescale i.MX8qxp Display Controller support Liu Ying
2025-05-14 9:05 ` Liu Ying
2026-07-14 19:36 ` Francesco Dolcini [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=20260714193627.GA9616@francesco-nb \
--to=francesco@dolcini.it \
--cc=Frank.Li@nxp.com \
--cc=agx@sigxcpu.org \
--cc=airlied@gmail.com \
--cc=aisheng.dong@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=lumag@kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=simona@ffwll.ch \
--cc=tglx@linutronix.de \
--cc=tzimmermann@suse.de \
--cc=u.kleine-koenig@baylibre.com \
--cc=victor.liu@nxp.com \
--cc=vkoul@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