From: Martin Kaiser <martin@kaiser.cx>
To: Shawn Guo <shawnguo@kernel.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Martin Kaiser <martin@kaiser.cx>
Subject: [PATCH 8/8] ARM: dts: imx25: mbimxsd25: native-mode is part of display-timings
Date: Thu, 1 Aug 2019 17:46:28 +0200 [thread overview]
Message-ID: <20190801154628.1624-9-martin@kaiser.cx> (raw)
In-Reply-To: <20190801154628.1624-1-martin@kaiser.cx>
Move the native-mode property inside the display-timings node.
According to
Documentation/devicetree/bindings/display/panel/display-timing.txt.
native-mode is a property of the display-timings node.
If it's located outside of display-timings, the native-mode setting is
ignored and the first display timing is used (which is a problem only if
someone adds another display timing).
Signed-off-by: Martin Kaiser <martin@kaiser.cx>
---
arch/arm/boot/dts/imx25-eukrea-mbimxsd25-baseboard-dvi-vga.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/imx25-eukrea-mbimxsd25-baseboard-dvi-vga.dts b/arch/arm/boot/dts/imx25-eukrea-mbimxsd25-baseboard-dvi-vga.dts
index d60d8f464ca9..24027a1fb46d 100644
--- a/arch/arm/boot/dts/imx25-eukrea-mbimxsd25-baseboard-dvi-vga.dts
+++ b/arch/arm/boot/dts/imx25-eukrea-mbimxsd25-baseboard-dvi-vga.dts
@@ -14,8 +14,8 @@
bits-per-pixel = <16>;
fsl,pcr = <0xfa208b80>;
bus-width = <18>;
- native-mode = <&dvi_vga_timings>;
display-timings {
+ native-mode = <&dvi_vga_timings>;
dvi_vga_timings: 640x480 {
clock-frequency = <31250000>;
hactive = <640>;
--
2.11.0
prev parent reply other threads:[~2019-08-01 15:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 15:46 [PATCH 0/8] move native-mode inside display-timings Martin Kaiser
2019-08-01 15:46 ` [PATCH 1/8] ARM: dts: imx27 phyCARD-S: native-mode is part of display-timings Martin Kaiser
2019-08-01 15:46 ` [PATCH 2/8] ARM: dts: imx25: mbimxsd25: " Martin Kaiser
2019-08-01 15:46 ` [PATCH 3/8] ARM: dts: eukrea-mbimxsd27: " Martin Kaiser
2019-08-01 15:46 ` [PATCH 4/8] ARM: dts: mbimxsd25: " Martin Kaiser
2019-08-01 15:46 ` [PATCH 5/8] ARM: dts: imx27-phytec-phycore-rdk: " Martin Kaiser
2019-08-01 15:46 ` [PATCH 6/8] ARM: dts: edb7211: " Martin Kaiser
2019-08-01 15:46 ` [PATCH 7/8] ARM: dts: apf27dev: " Martin Kaiser
2019-08-01 15:46 ` Martin Kaiser [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=20190801154628.1624-9-martin@kaiser.cx \
--to=martin@kaiser.cx \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--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 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).