From: Frank Li <Frank.li@oss.nxp.com>
To: Liu Ying <victor.liu@nxp.com>
Cc: Alexander Stein <alexander.stein@ew.tq-group.com>,
Frank Li <Frank.Li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Dong Aisheng <aisheng.dong@nxp.com>,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux@ew.tq-group.com
Subject: Re: [PATCH v2 2/5] arm64: dts: imx8qxp: Add display controller subsystem
Date: Thu, 15 Oct 2026 11:22:33 -0500 [thread overview]
Message-ID: <atD9yeOeHZiKzhZD@SMW015318> (raw)
In-Reply-To: <atBLglf0gSLS7XkW@raspi>
On Thu, Oct 15, 2026 at 11:41:54AM +0800, Liu Ying wrote:
> Hi Alexander,
>
> On Wed, Oct 14, 2026 at 09:16:46AM +0200, Alexander Stein wrote:
>
> [...]
>
...
> > +
> > + dc0_framegen1: framegen@5618d400 {
> > + reg = <0x5618d400 0x98>;
> > + clocks = <&dc0_disp_lpcg IMX_LPCG_CLK_1>;
> > + interrupt-parent = <&dc0_intc>;
> > + interrupts = <28>, <29>, <30>, <31>,
> > + <45>, <46>, <47>, <48>;
> > + interrupt-names = "int0", "int1", "int2", "int3",
> > + "primsync_on", "primsync_off",
> > + "secsync_on", "secsync_off";
> > + };
> > +
> > + dc0_tcon1: tcon@5618e400 {
> > + reg = <0x5618e400 0x588>;
> > +
> > + port {
> > + dc0_disp1_dc0_pixel_combiner_ch1: endpoint {
> > + remote-endpoint = <&dc0_pixel_combiner_ch1_dc0_disp1>;
> > + };
> > + };
> > + };
> > + };
> > + };
>
> I'm thinking that it would be good to have a complete display controller
> DT node in the first place, including those prefetch engines attached to
> fetchunits through the fsl,prg property.
what's current prefetch engines status? Is it possible merge at v7.5 ?
Frank
> In this way, display controller
> driver's life would be easier - all child/grandchild devices are always
> available. I'm considering to adding a check to the Linux display controller
> driver to ensure the availability(at least for critical child/grandchild
> devices).
>
> --
> Regards,
> Liu Ying
>
next prev parent reply other threads:[~2026-10-15 16:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 7:16 [PATCH v2 0/5] LVDS support for TQMa8Xx Alexander Stein
2026-10-14 7:16 ` [PATCH v2 1/5] dt-bindings: firmware: imx: Add SCU controlled display pixel link nodes Alexander Stein
2026-10-14 7:16 ` [PATCH v2 2/5] arm64: dts: imx8qxp: Add display controller subsystem Alexander Stein
2026-10-14 13:55 ` Frank Li
2026-10-15 6:31 ` Francesco Dolcini
2026-10-15 8:25 ` Alexander Stein
2026-10-15 3:41 ` Liu Ying
2026-10-15 16:22 ` Frank Li [this message]
2026-10-14 7:16 ` [PATCH v2 3/5] arm64: dts: imx8qxp: Add MIPI-LVDS combo subsystems Alexander Stein
2026-10-14 14:01 ` Frank Li
2026-10-15 8:09 ` Alexander Stein
2026-10-14 7:16 ` [PATCH v2 4/5] arm64: dts: freescale: Add LVDS overlays for TQMa8Xx Alexander Stein
2026-10-14 7:16 ` [PATCH v2 5/5] arm64: dts: freescale: Add dual-channel LVDS overlay " Alexander Stein
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=atD9yeOeHZiKzhZD@SMW015318 \
--to=frank.li@oss.nxp.com \
--cc=Frank.Li@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@ew.tq-group.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=victor.liu@nxp.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