From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-9.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED,USER_AGENT_GIT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 25E89C4CEC9 for ; Wed, 18 Sep 2019 19:39:40 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id EB92E22451 for ; Wed, 18 Sep 2019 19:39:39 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731678AbfIRTjj (ORCPT ); Wed, 18 Sep 2019 15:39:39 -0400 Received: from viti.kaiser.cx ([85.214.81.225]:58292 "EHLO viti.kaiser.cx" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727648AbfIRTjj (ORCPT ); Wed, 18 Sep 2019 15:39:39 -0400 Received: from dslb-084-059-234-127.084.059.pools.vodafone-ip.de ([84.59.234.127] helo=martin-debian-1.paytec.ch) by viti.kaiser.cx with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from ) id 1iAfnW-0001vE-I4; Wed, 18 Sep 2019 21:39:30 +0200 From: Martin Kaiser To: Shawn Guo , Bartlomiej Zolnierkiewicz , Rob Herring , Pengutronix Kernel Team , NXP Linux Team Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Martin Kaiser Subject: [PATCH] dt-bindings: display: imx: fix native-mode setting Date: Wed, 18 Sep 2019 21:38:53 +0200 Message-Id: <20190918193853.25689-1-martin@kaiser.cx> X-Mailer: git-send-email 2.11.0 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. We've already fixed the board definitions which got this wrong. Fix the example in the imx framebuffer bindings as well. Signed-off-by: Martin Kaiser --- Documentation/devicetree/bindings/display/imx/fsl,imx-fb.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/devicetree/bindings/display/imx/fsl,imx-fb.txt b/Documentation/devicetree/bindings/display/imx/fsl,imx-fb.txt index e5a8b363d829..f4df9e83bcd2 100644 --- a/Documentation/devicetree/bindings/display/imx/fsl,imx-fb.txt +++ b/Documentation/devicetree/bindings/display/imx/fsl,imx-fb.txt @@ -38,10 +38,10 @@ Example: display0: display0 { model = "Primeview-PD050VL1"; - native-mode = <&timing_disp0>; bits-per-pixel = <16>; fsl,pcr = <0xf0c88080>; /* non-standard but required */ display-timings { + native-mode = <&timing_disp0>; timing_disp0: 640x480 { hactive = <640>; vactive = <480>; -- 2.11.0