From: Shawn Guo <shawnguo2@yeah.net>
To: Liu Ying <victor.liu@nxp.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, robh@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com
Subject: Re: [PATCH] arm64: dts: imx8mp-evk: Fix hdmi@3d node
Date: Sun, 25 Feb 2024 21:28:44 +0800 [thread overview]
Message-ID: <ZdtAjE2SylK8plBB@dragon> (raw)
In-Reply-To: <20240223025738.2486807-1-victor.liu@nxp.com>
On Fri, Feb 23, 2024 at 10:57:38AM +0800, Liu Ying wrote:
> The hdmi@3d node's compatible string is "adi,adv7535" instead of
> "adi,adv7533" or "adi,adv751*".
>
> Fix the hdmi@3d node by means of:
> * Use default register addresses for "cec", "edid" and "packet", because
> there is no need to use a non-default address map.
> * Add missing interrupt related properties.
> * Drop "adi,input-*" properties which are only valid for adv751*.
> * Add VEXT_3V3 fixed regulator.
> * Add "*-supply" properties, since most are required.
> * Fix label names - s/adv7533/adv7535/.
>
> Fixes: 65344b9bed3a ("arm64: dts: imx8mp-evk: Add HDMI support")
> Signed-off-by: Liu Ying <victor.liu@nxp.com>
Applied, thanks!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo2@yeah.net>
To: Liu Ying <victor.liu@nxp.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, robh@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com
Subject: Re: [PATCH] arm64: dts: imx8mp-evk: Fix hdmi@3d node
Date: Sun, 25 Feb 2024 21:28:44 +0800 [thread overview]
Message-ID: <ZdtAjE2SylK8plBB@dragon> (raw)
In-Reply-To: <20240223025738.2486807-1-victor.liu@nxp.com>
On Fri, Feb 23, 2024 at 10:57:38AM +0800, Liu Ying wrote:
> The hdmi@3d node's compatible string is "adi,adv7535" instead of
> "adi,adv7533" or "adi,adv751*".
>
> Fix the hdmi@3d node by means of:
> * Use default register addresses for "cec", "edid" and "packet", because
> there is no need to use a non-default address map.
> * Add missing interrupt related properties.
> * Drop "adi,input-*" properties which are only valid for adv751*.
> * Add VEXT_3V3 fixed regulator.
> * Add "*-supply" properties, since most are required.
> * Fix label names - s/adv7533/adv7535/.
>
> Fixes: 65344b9bed3a ("arm64: dts: imx8mp-evk: Add HDMI support")
> Signed-off-by: Liu Ying <victor.liu@nxp.com>
Applied, thanks!
next prev parent reply other threads:[~2024-02-25 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 2:57 [PATCH] arm64: dts: imx8mp-evk: Fix hdmi@3d node Liu Ying
2024-02-23 2:57 ` Liu Ying
2024-02-25 13:28 ` Shawn Guo [this message]
2024-02-25 13:28 ` Shawn Guo
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=ZdtAjE2SylK8plBB@dragon \
--to=shawnguo2@yeah.net \
--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@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--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 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.