From: Marek Vasut <marex@nabladev.com>
To: Liu Ying <victor.liu@nxp.com>, Piyush Patle <piyushpatle228@gmail.com>
Cc: dri-devel@lists.freedesktop.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, daniel.baluta@nxp.com,
Frank.Li@nxp.com, shawnguo@kernel.org, tzimmermann@suse.de,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
airlied@gmail.com, simona@ffwll.ch
Subject: Re: [RFC] drm/imx: upstream direction for i.MX95 display support
Date: Mon, 21 Sep 2026 20:40:38 +0200 [thread overview]
Message-ID: <c43103f6-348c-48b9-a831-ecb9379ce46f@nabladev.com> (raw)
In-Reply-To: <akxjwULa-p6c6IvR@raspi>
On 7/7/26 4:26 AM, Liu Ying wrote:
Hi,
> I need to point out that i.MX95 display controller also has 2 display engines
> and 1 pixel engine, which is something missing in your code. This makes me
> think that you have no enough i.MX95 display controller documents.
>
> Generally speaking, I'd say there is a lot to be improved before posting the
> formal patch series. Gut feeling is that maybe it's a bit too difficult
> for you to get the drivers right. As I said earlier, my original plan is to
> add i.MX8QXP prefetch engine support first with the posted patch series and
> then to add i.MX95 display controller support, but maybe I can try to add the
> latter first - just need to find a time slot. However, adding prefetch engine
> support first would directly show a reason to people why two DRM drivers are
> warranted when adding i.MX95 display controller support.
I haven't seen any MX95 DPU patches posted (except for my work from last
year), was there any progress since this discussion ?
prev parent reply other threads:[~2026-09-21 18:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 10:03 [RFC] drm/imx: upstream direction for i.MX95 display support Piyush Patle
2026-06-26 9:53 ` Liu Ying
2026-06-26 19:53 ` Piyush Patle
2026-07-04 22:03 ` Piyush Patle
2026-07-06 2:38 ` Liu Ying
[not found] ` <CAMB+xkY2rut-sEUMyFnXqYCNmyseP4nAGj4BfreORTTM=SN8_g@mail.gmail.com>
2026-07-06 10:32 ` Liu Ying
2026-07-06 15:01 ` Piyush Patle
2026-07-07 2:26 ` Liu Ying
2026-09-21 18:40 ` Marek Vasut [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=c43103f6-348c-48b9-a831-ecb9379ce46f@nabladev.com \
--to=marex@nabladev.com \
--cc=Frank.Li@nxp.com \
--cc=airlied@gmail.com \
--cc=daniel.baluta@nxp.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=imx@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=piyushpatle228@gmail.com \
--cc=shawnguo@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.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