From: Peng Fan <peng.fan@oss.nxp.com>
To: Yannic Moog <y.moog@phytec.de>
Cc: Shawn Guo <shawnguo@kernel.org>,
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>,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
upstream@lists.phytec.de
Subject: Re: [PATCH v3 4/4] arm64: dts: imx8mp pollux: add displays for expansion board
Date: Sat, 11 Oct 2025 21:14:15 +0800 [thread overview]
Message-ID: <20251011131415.GE20642@nxa18884-linux.ap.freescale.net> (raw)
In-Reply-To: <20251001-imx8mp-pollux-display-overlays-v3-4-87f843f6bed6@phytec.de>
On Wed, Oct 01, 2025 at 02:33:54PM +0200, Yannic Moog wrote:
>The same displays that can be connected directly to the
>imx8mp-phyboard-pollux can also be connected to the expansion board
>PEB-AV-10. For displays connected to the expansion board, a second LVDS
>channel of the i.MX 8M Plus SoC is used and only a single display
>connected to the SoC LVDS display bridge at a given time is supported.
>
>Signed-off-by: Yannic Moog <y.moog@phytec.de>
Reviewed-by: Peng Fan <peng.fan@nxp.com>
prev parent reply other threads:[~2025-10-11 12:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 12:33 [PATCH v3 0/4] Add display overlays for imx8mp-phyboard-pollux Yannic Moog
2025-10-01 12:33 ` [PATCH v3 1/4] arm64: dts: im8mp-phy{board,core}: update license and copyright Yannic Moog
2025-10-01 14:44 ` Frank Li
2025-10-11 13:06 ` Peng Fan
2025-10-13 5:45 ` Yannic Moog
2025-10-01 12:33 ` [PATCH v3 2/4] arm64: dts: imx8mp pollux: add display overlays Yannic Moog
2025-10-11 13:08 ` Peng Fan
2025-10-01 12:33 ` [PATCH v3 3/4] arm64: dts: imx8mp pollux: add expansion board overlay Yannic Moog
2025-10-11 13:13 ` Peng Fan
2025-10-01 12:33 ` [PATCH v3 4/4] arm64: dts: imx8mp pollux: add displays for expansion board Yannic Moog
2025-10-11 13:14 ` Peng Fan [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=20251011131415.GE20642@nxa18884-linux.ap.freescale.net \
--to=peng.fan@oss.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=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=upstream@lists.phytec.de \
--cc=y.moog@phytec.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
all inboxes | Powered by JetHome®