linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Foss <robert.foss@collabora.com>
To: shawnguo@kernel.org, s.hauer@pengutronix.de,
	kernel@pengutronix.de, fabio.estevam@nxp.com, linux-imx@nxp.com,
	robh+dt@kernel.org, mark.rutland@arm.com,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: Robert Foss <robert.foss@collabora.com>
Subject: [PATCH] ARM: dts: imx6qdl-nitrogen6_max: Disable LVDS channels
Date: Mon,  8 Apr 2019 19:53:19 +0200	[thread overview]
Message-ID: <20190408175319.9106-1-robert.foss@collabora.com> (raw)

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 <robert.foss@collabora.com>
---
 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";
 
 		port@4 {
 			reg = <4>;
-- 
2.19.1


             reply	other threads:[~2019-04-08 17:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-08 17:53 Robert Foss [this message]
2019-04-08 20:37 ` [PATCH] ARM: dts: imx6qdl-nitrogen6_max: Disable LVDS channels Fabio Estevam
2019-04-09  0:07   ` Robert Foss
2019-04-10  7:35     ` Gary Bisson
2019-04-10 10:57       ` Robert Foss
2019-04-10 11:55         ` Fabio Estevam
2019-04-10 12:00           ` Fabio Estevam

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=20190408175319.9106-1-robert.foss@collabora.com \
    --to=robert.foss@collabora.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fabio.estevam@nxp.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --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).