Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp3366311yba; Mon, 8 Apr 2019 17:36:03 -0700 (PDT) X-Google-Smtp-Source: APXvYqxIHbbxWM0F9nSmDBhCV/KVvfYxTWvV+i2Nx1S404O9P4sTf+u4tSTVJrA7bzqVSgQ0+g8+ X-Received: by 2002:aa7:8694:: with SMTP id d20mr33698800pfo.81.1554770163245; Mon, 08 Apr 2019 17:36:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554770163; cv=none; d=google.com; s=arc-20160816; b=BVX91yvDDiHtY7Xg7e5xcwGLLnHOSabdxCTkxeO3pjg33N4E05J51BgYusk7/QCwFF kKw0hHoKFfgQOlQPdzTUmwnPkCNVMnKn5Z3IGPnfJIyBOtN2d6JCmYJLKDbEImEkhE6I Mn7iDwhsU4ydd376Gjese54b63hGG9tqWKZDmiNu4jSl3iTz9yRbsnT/Ucg57ZpzgEkX kHmGkYkfOJyyBdk+8UHKwnhsOJ4owcpe2ifSGNZOkgCCZabi6Uww2rENV2py+VvY1QlZ BaopA/LK7ZAO80g9+wXd3BoFz1DDSk7mpqq65HGFafM7aEyUeqJUQXM2Egb3lO2GlGni Ehyg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=OGoM9JgMYgmT6HnzfBImFp1qiFDXNz8BiMvukO8Y5mc=; b=v2bTg+AISTYost1y0VFhHAtWMcgIUu8hsvJgwiZxXTnVo0IRAMfKC/6yCZjT7+mzXt rWou9z9qS8pn+xkGsobaY65o0up7Tta+z+SeWWGwRA7AqE1B3oM6KvRaJ8cGcd0cXm96 NgfTYMAlNkO/HfR6GB64kKySoBqyRzg7ygHyVB9FtTJ2RT9uCm7jFkDqTT+x7YWcPm4t hMrRpAEsvLOfYdguNesCJSxkOvru8nOB/7yN7mn6cx6LLAq7uHuhoK01BMDHTL7WrP2B /PpCDRlKsDDg44ugUBHUBJyNWdPmu6a+kbdNgOrb9yvpfhJrQLcqetBS33KbPMCOtHZh EgHw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x3si16920421plo.274.2019.04.08.17.35.46; Mon, 08 Apr 2019 17:36:03 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726501AbfDIAHo (ORCPT + 99 others); Mon, 8 Apr 2019 20:07:44 -0400 Received: from bhuna.collabora.co.uk ([46.235.227.227]:47500 "EHLO bhuna.collabora.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726068AbfDIAHo (ORCPT ); Mon, 8 Apr 2019 20:07:44 -0400 Received: from [IPv6:2a02:2450:102f:3e0:845d:198:7d0e:69e8] (unknown [IPv6:2a02:2450:102f:3e0:845d:198:7d0e:69e8]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: robertfoss) by bhuna.collabora.co.uk (Postfix) with ESMTPSA id F0E84263AF8; Tue, 9 Apr 2019 01:07:41 +0100 (BST) Subject: Re: [PATCH] ARM: dts: imx6qdl-nitrogen6_max: Disable LVDS channels To: Fabio Estevam , Gary Bisson Cc: Shawn Guo , Sascha Hauer , Sascha Hauer , Fabio Estevam , NXP Linux Team , Rob Herring , Mark Rutland , "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , linux-kernel References: <20190408175319.9106-1-robert.foss@collabora.com> From: Robert Foss Message-ID: <4fd506a1-c961-0569-6d39-283758f363d9@collabora.com> Date: Tue, 9 Apr 2019 02:07:25 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hey Fabio, On 4/8/19 10:37 PM, Fabio Estevam wrote: > Hi Robert, > > [Adding Gary] > > On Mon, Apr 8, 2019 at 2:54 PM Robert Foss wrote: >> >> If a LVDS device is not connected, having the LVDS channels >> enabled will prevent imx-ldb from probing correctly even >> if other CRTCs are connected. >> >> Signed-off-by: Robert Foss >> --- >> arch/arm/boot/dts/imx6qdl-nitrogen6_max.dtsi | 4 ++-- >> 1 file changed, 2 insertions(+), 2 deletions(-) >> >> diff --git a/arch/arm/boot/dts/imx6qdl-nitrogen6_max.dtsi b/arch/arm/boot/dts/imx6qdl-nitrogen6_max.dtsi >> index 39200e5dc896..5b413cf4c250 100644 >> --- a/arch/arm/boot/dts/imx6qdl-nitrogen6_max.dtsi >> +++ b/arch/arm/boot/dts/imx6qdl-nitrogen6_max.dtsi >> @@ -703,7 +703,7 @@ >> status = "okay"; >> >> lvds-channel@0 { >> - status = "okay"; >> + status = "disabled"; >> >> port@4 { >> reg = <4>; >> @@ -715,7 +715,7 @@ >> }; >> >> lvds-channel@1 { >> - status = "okay"; >> + status = "disabled"; > > I am not sure I understood what you are trying to fix. If CONFIG_DRM_IMX_LDB is enabled, LVDS DT channels are enabled and no LVDS-panels are connected the imx-ldb driver will fail to bind. This is a problem, since it will prevent other actually connected display output from being used, even if they bind properly. > > Could you please share some logs when imx-ldb fails to probe correctly? [ 2.119563] component_bind_all() trying to bind: ldb [ 2.124600] imx-drm display-subsystem: binding ldb (ops imx_ldb_ops) [ 2.146169] drm_of_find_panel_or_bridge() np->name=lvds-channel np->type= [ 2.153709] drm_of_find_panel_or_bridge() no panel found for remote [ 2.160081] drm_of_find_panel_or_bridge() bridge needed [ 2.162043] drm_of_find_panel_or_bridge() bridge not found [ 2.165331] drm_of_find_panel_or_bridge() failed [ 2.170023] imx-drm display-subsystem: failed to bind ldb (ops imx_ldb_ops): -517 This at the same time as HDMI binds properly: [ 4.458954] dwhdmi-imx 120000.hdmi: Detected HDMI TX controller v1.30a with HDCP (DWC HDMI 3D TX PHY) [ 4.469633] imx-drm display-subsystem: bound 120000.hdmi (ops dw_hdmi_imx_ops) Which in the end causes the IMX driver to not initialize properly and ignore the HDMI connection that bound properly. This in turn prevents us from having any graphical output while there is no LVDS panel connected. > > Is this a regression? > Not as far as I know. How a Nitrogen6-Max board without a LVDS panel, but using the imx_v6_v7_defconfig ever started and had displayed graphical output on other connected displays I don't know though. Rob.