From: Shawn Guo <shawnguo2@yeah.net>
To: Marek Vasut <marex@denx.de>
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>,
Shawn Guo <shawnguo@kernel.org>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
kernel@dh-electronics.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: imx8mp: Enable HDMI on i.MX8MP DHCOM PDK2 and PDK3
Date: Sat, 15 Jun 2024 16:06:12 +0800 [thread overview]
Message-ID: <Zm1LdFyxYJ1+UIgY@dragon> (raw)
In-Reply-To: <20240514010706.245874-1-marex@denx.de>
On Tue, May 14, 2024 at 03:06:42AM +0200, Marek Vasut wrote:
> Enable HDMI output on i.MX8MP DHCOM PDK2 and PDK3. The I2C5 on PDK2 and
> I2C mux port 1 on PDK3 respectively are used in regular I2C mode instead
> of HDMI DDC mode to permit connection of other I2C devices on those buses.
> The pinctrl_hdmi node is part of the SoM DTSI already.
>
> Signed-off-by: Marek Vasut <marex@denx.de>
Applied, thanks!
prev parent reply other threads:[~2024-06-15 8:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 1:06 [PATCH] arm64: dts: imx8mp: Enable HDMI on i.MX8MP DHCOM PDK2 and PDK3 Marek Vasut
2024-05-14 1:06 ` Marek Vasut
2024-05-14 12:53 ` Rob Herring (Arm)
2024-05-14 12:53 ` Rob Herring (Arm)
2024-05-14 22:18 ` Marek Vasut
2024-05-14 22:18 ` Marek Vasut
2024-05-16 8:00 ` Francesco Dolcini
2024-05-16 8:00 ` Francesco Dolcini
2024-05-16 11:14 ` Marek Vasut
2024-05-16 11:14 ` Marek Vasut
2024-05-16 11:36 ` Ahmad Fatoum
2024-05-16 11:36 ` Ahmad Fatoum
2024-05-16 11:44 ` Marek Vasut
2024-05-16 11:44 ` Marek Vasut
2024-05-16 11:46 ` Ahmad Fatoum
2024-05-16 11:46 ` Ahmad Fatoum
2024-05-16 12:07 ` Alexander Stein
2024-05-16 12:07 ` Alexander Stein
2024-05-16 11:57 ` Francesco Dolcini
2024-05-16 11:57 ` Francesco Dolcini
2024-06-15 8:06 ` Shawn Guo [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=Zm1LdFyxYJ1+UIgY@dragon \
--to=shawnguo2@yeah.net \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@dh-electronics.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.