From: Shawn Guo <shawnguo@kernel.org>
To: Adam Ford <aford173@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org, aford@beaconembedded.com,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3 0/3] arm64: dts: imx8mn/imx8mm-beacon: Add HDMI
Date: Tue, 18 Jul 2023 09:27:49 +0800 [thread overview]
Message-ID: <20230718012749.GR9559@dragon> (raw)
In-Reply-To: <20230615215314.5402-1-aford173@gmail.com>
On Thu, Jun 15, 2023 at 04:53:10PM -0500, Adam Ford wrote:
> The DSI updates are in the DRM tree and Linux next with some updates
> that now allow the DSI to connect to an HDMI bridge and successfully
> sync displays at various resolutions and refresh rates.
>
>
> V3: Alphabetize regulator names.
> Add register names for EDID and Packet
> Add I2C address change for the camera since it
> conflicted with the I2C address of the HDMI bridge.
>
> V2: Make 'compatible' the first thing in the new nodes.
>
> Adam Ford (3):
> arm64: dts: imx8mn-beacon: Add HDMI video with sound
> arm64: dts: imx8mm-beacon: Change camera I2C address
> arm64: dts: imx8mm-beacon: Add HDMI video with sound
Applied all, thanks!
next prev parent reply other threads:[~2023-07-18 1:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 21:53 [PATCH V3 0/3] arm64: dts: imx8mn/imx8mm-beacon: Add HDMI Adam Ford
2023-06-15 21:53 ` [PATCH 1/3] arm64: dts: imx8mn-beacon: Add HDMI video with sound Adam Ford
2023-06-15 21:53 ` [PATCH 2/3] arm64: dts: imx8mm-beacon: Change camera I2C address Adam Ford
2023-06-15 21:53 ` [PATCH 3/3] arm64: dts: imx8mm-beacon: Add HDMI video with sound Adam Ford
2023-06-22 16:09 ` [PATCH V3 0/3] arm64: dts: imx8mn/imx8mm-beacon: Add HDMI Adam Ford
2023-07-18 1:27 ` Shawn Guo [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-10 19:26 Adam Ford
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=20230718012749.GR9559@dragon \
--to=shawnguo@kernel.org \
--cc=aford173@gmail.com \
--cc=aford@beaconembedded.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).