From mboxrd@z Thu Jan 1 00:00:00 1970 From: Martin Kaiser Subject: [PATCH 3/8] ARM: dts: eukrea-mbimxsd27: native-mode is part of display-timings Date: Thu, 1 Aug 2019 17:46:23 +0200 Message-ID: <20190801154628.1624-4-martin@kaiser.cx> References: <20190801154628.1624-1-martin@kaiser.cx> Return-path: In-Reply-To: <20190801154628.1624-1-martin@kaiser.cx> Sender: linux-kernel-owner@vger.kernel.org To: Shawn Guo , Pengutronix Kernel Team , Fabio Estevam , NXP Linux Team Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Martin Kaiser List-Id: devicetree@vger.kernel.org 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 --- arch/arm/boot/dts/imx27-eukrea-mbimxsd27-baseboard.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/imx27-eukrea-mbimxsd27-baseboard.dts b/arch/arm/boot/dts/imx27-eukrea-mbimxsd27-baseboard.dts index 84fc8df4be7c..9c3ec82ec7e5 100644 --- a/arch/arm/boot/dts/imx27-eukrea-mbimxsd27-baseboard.dts +++ b/arch/arm/boot/dts/imx27-eukrea-mbimxsd27-baseboard.dts @@ -11,11 +11,11 @@ display0: CMO-QVGA { model = "CMO-QVGA"; - native-mode = <&timing0>; bits-per-pixel = <16>; fsl,pcr = <0xfad08b80>; display-timings { + native-mode = <&timing0>; timing0: 320x240 { clock-frequency = <6500000>; hactive = <320>; -- 2.11.0