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 <mar...@kaiser.cx>
---
 arch/arm/boot/dts/imx27-phytec-phycard-s-rdk.dts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/arm/boot/dts/imx27-phytec-phycard-s-rdk.dts 
b/arch/arm/boot/dts/imx27-phytec-phycard-s-rdk.dts
index 5e5e282ed30e..0cd75dadf292 100644
--- a/arch/arm/boot/dts/imx27-phytec-phycard-s-rdk.dts
+++ b/arch/arm/boot/dts/imx27-phytec-phycard-s-rdk.dts
@@ -15,10 +15,10 @@
 
        display: display {
                model = "Primeview-PD050VL1";
-               native-mode = <&timing0>;
                bits-per-pixel = <16>;  /* non-standard but required */
                fsl,pcr = <0xf0c88080>; /* non-standard but required */
                display-timings {
+                       native-mode = <&timing0>;
                        timing0: 640x480 {
                                hactive = <640>;
                                vactive = <480>;
-- 
2.11.0

Reply via email to