From: Sascha Hauer <sha@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org, Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH v2] ARM: dts: fix wrong display-timings native-mode binding
Date: Wed, 4 Jan 2023 11:51:57 +0100 [thread overview]
Message-ID: <20230104105157.GR11668@pengutronix.de> (raw)
In-Reply-To: <20221221102627.3059068-1-a.fatoum@pengutronix.de>
On Wed, Dec 21, 2022 at 11:26:27AM +0100, Ahmad Fatoum wrote:
> The value of the native-mode property is supposed to be a phandle to
> the entry in question, but instead the full node path was used because
> the <angle brackets> were missing. Fix this. This should not involve any
> functional change as the default mode would've been the first element,
> which is the same element the malformed native-mode was meant to point
> at anyway.
>
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
> arch/arm/dts/imx6q-var-custom.dts | 2 +-
> arch/arm/dts/imx6qdl-skov-imx6.dtsi | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
Applied, thanks
Sascha
>
> diff --git a/arch/arm/dts/imx6q-var-custom.dts b/arch/arm/dts/imx6q-var-custom.dts
> index ddb220fb0ad4..cbfe4da7e1b4 100644
> --- a/arch/arm/dts/imx6q-var-custom.dts
> +++ b/arch/arm/dts/imx6q-var-custom.dts
> @@ -83,7 +83,7 @@
> fsl,data-width = <24>;
> status = "okay";
> display-timings {
> - native-mode = &claawvga;
> + native-mode = <&claawvga>;
> claawvga: claawvga {
> native-mode;
> clock-frequency = <35714000>;
> diff --git a/arch/arm/dts/imx6qdl-skov-imx6.dtsi b/arch/arm/dts/imx6qdl-skov-imx6.dtsi
> index f4610ee1e7ba..cb4224f1b441 100644
> --- a/arch/arm/dts/imx6qdl-skov-imx6.dtsi
> +++ b/arch/arm/dts/imx6qdl-skov-imx6.dtsi
> @@ -146,7 +146,7 @@
> };
>
> display-timings {
> - native-mode = &l2rt;
> + native-mode = <&l2rt>;
>
> l2rt: l2rt {
> native-mode;
> @@ -190,7 +190,7 @@
> /* power-supply = <®_3p3v>; */
>
> display-timings {
> - native-mode = &mi1010ait_1cp1;
> + native-mode = <&mi1010ait_1cp1>;
>
> mi1010ait_1cp1: mi1010ait-1cp1 {
> native-mode;
> --
> 2.30.2
>
>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2023-01-04 10:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 10:26 Ahmad Fatoum
2022-12-21 11:35 ` Sam Ravnborg
2023-01-04 10:51 ` Sascha Hauer [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=20230104105157.GR11668@pengutronix.de \
--to=sha@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=sam@ravnborg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox