Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: Frank Li <Frank.li@nxp.com>
To: Marek Vasut <marex@nabladev.com>
Cc: linux-arm-kernel@lists.infradead.org,
	Conor Dooley <conor+dt@kernel.org>,
	Fabio Estevam <festevam@gmail.com>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Rob Herring <robh@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	devicetree@vger.kernel.org, imx@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/6] arm64: dts: imx8mm: imx8mp: Add LVDS DTOs for Data Modul i.MX8M Mini and Plus eDM SBC
Date: Fri, 8 May 2026 11:46:03 -0400	[thread overview]
Message-ID: <af4FO5vOx3ruwWBE@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <65342735-44b3-4a2b-90ab-6093e0fd91c9@nabladev.com>

On Fri, May 08, 2026 at 01:21:43PM +0200, Marek Vasut wrote:
> On 4/7/26 11:17 PM, Marek Vasut wrote:
> > Add DT overlay for the DSI-to-LVDS adapter eDM-MOD-iMX8Mm-LVDS populated
> > with Lontium LT9211 bridge. This adapter can be optionally populated onto
> > the eDM SBC. This adapter can be extended with multiple panels, currently
> > supported are the following:
> >
> > - AUO G215HVN011
> > - Innolux G070Y2-L01
> > - Innolux G101ICE-L01
> > - Innolux G121XCE-L01
> > - Innolux G156HCE-L01
> > - Multi-Inno Technology MI0700A2T-30
> > - Multi-Inno Technology MI1010Z1T-1CP11
> >
> > Note that in case of the i.MX8M Plus eDM SBC, the adapter name containing
> > iMX8Mm is not a typo, this is the adapter model string. The adapter was
> > originally developed for the iMX8Mm eDM SBC.
>
> Hello Frank,
>
> this patchset is now split. How can we proceed ?

I am thinking about it. I found an old thread
https://lore.kernel.org/linux-devicetree/20250902105710.00512c6d@booty/

The current code base already supportted partitial of it, such as gpio and
irq map for connector.

Internal chancel liu have prepared version by use nexus mapping for audio
boards, which almost done to send out to review.

I want to wait for a little bit well to resolve or partitial resolve N x M
problem.

Frank

>
> Thank you for your help!

  reply	other threads:[~2026-05-08 15:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-07 21:17 [PATCH v3 1/6] arm64: dts: imx8mm: imx8mp: Add LVDS DTOs for Data Modul i.MX8M Mini and Plus eDM SBC Marek Vasut
2026-04-07 21:17 ` [PATCH v3 2/6] arm64: dts: imx8mm: imx8mp: Add legacy board " Marek Vasut
2026-04-07 21:17 ` [PATCH v3 3/6] arm64: dts: imx8mm: imx8mp: Add HDMI " Marek Vasut
2026-04-07 21:17 ` [PATCH v3 4/6] arm64: dts: imx8mm: imx8mp: Add CM " Marek Vasut
2026-04-07 21:17 ` [PATCH v3 5/6] arm64: dts: imx8mm: imx8mp: Add FIO1 " Marek Vasut
2026-04-07 21:17 ` [PATCH v3 6/6] arm64: dts: imx8mm: imx8mp: Add FIO1-Audio " Marek Vasut
2026-05-08 11:21 ` [PATCH v3 1/6] arm64: dts: imx8mm: imx8mp: Add LVDS " Marek Vasut
2026-05-08 15:46   ` Frank Li [this message]
2026-05-08 16:20     ` Marek Vasut
2026-05-08 20:15       ` Frank Li
2026-05-08 21:47         ` Marek Vasut

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=af4FO5vOx3ruwWBE@lizhi-Precision-Tower-5810 \
    --to=frank.li@nxp.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=marex@nabladev.com \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    /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