Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Ash Charles <ashcharles@gmail.com>
To: linux-omap@vger.kernel.org, devicetree@vger.kernel.org
Cc: tony@atomide.com, bcousson@baylibre.com,
	Adam YH Lee <adam.yh.lee@gmail.com>
Subject: [PATCH 1/5] omap3: overo: Update LCD panel names
Date: Fri, 12 Jun 2015 13:37:22 -0700	[thread overview]
Message-ID: <1434141446-11568-2-git-send-email-ashcharles@gmail.com> (raw)
In-Reply-To: <1434141446-11568-1-git-send-email-ashcharles@gmail.com>

From: Adam YH Lee <adam.yh.lee@gmail.com>

For Gumstix Overo COMs, the u-boot bootloader typically passes an
argument specifying the default display via the omapdss.def_disp
parameter.  When a default display is specified, DSS2 tries to match
this name with either the device tree label (e.g. label=dvi) or,
failing this, the device tree alias (e.g. label=display0). Update the
panel names for the 'lcd43' and 'lcd35' displays in the device tree
such that they match the names passed by u-boot.

Signed-off-by: Ash Charles <ashcharles@gmail.com>
---
 arch/arm/boot/dts/omap3-overo-common-lcd35.dtsi | 2 +-
 arch/arm/boot/dts/omap3-overo-common-lcd43.dtsi | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/arm/boot/dts/omap3-overo-common-lcd35.dtsi b/arch/arm/boot/dts/omap3-overo-common-lcd35.dtsi
index 233c69e50ae3..df8908adb0cb 100644
--- a/arch/arm/boot/dts/omap3-overo-common-lcd35.dtsi
+++ b/arch/arm/boot/dts/omap3-overo-common-lcd35.dtsi
@@ -120,7 +120,7 @@
 
 	lcd0: display@0 {
 		compatible = "lgphilips,lb035q02";
-		label = "lcd";
+		label = "lcd35";
 
 		reg = <1>;					/* CS1 */
 		spi-max-frequency = <10000000>;
diff --git a/arch/arm/boot/dts/omap3-overo-common-lcd43.dtsi b/arch/arm/boot/dts/omap3-overo-common-lcd43.dtsi
index f5395b7da912..048fd216970a 100644
--- a/arch/arm/boot/dts/omap3-overo-common-lcd43.dtsi
+++ b/arch/arm/boot/dts/omap3-overo-common-lcd43.dtsi
@@ -98,7 +98,7 @@
 
 	lcd0: display@0 {
 		compatible = "samsung,lte430wq-f0c", "panel-dpi";
-		label = "lcd";
+		label = "lcd43";
 
 		pinctrl-names = "default";
 		pinctrl-0 = <&lte430_pins>;
-- 
2.1.4


  reply	other threads:[~2015-06-12 20:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-12 20:37 [PATCH 0/5] Device Tree Fixes for Overo Ash Charles
2015-06-12 20:37 ` Ash Charles [this message]
     [not found]   ` <1434141446-11568-2-git-send-email-ashcharles-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-07-14  6:48     ` [PATCH 1/5] omap3: overo: Update LCD panel names Tony Lindgren
2015-06-12 20:37 ` [PATCH 2/5] omap3: dts: Add DTS for Gumstix TobiDuo expansion board Ash Charles
     [not found]   ` <1434141446-11568-3-git-send-email-ashcharles-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-07-14 11:01     ` Tony Lindgren
2015-06-12 20:37 ` [PATCH 3/5] omap3: overo: Enable McBSP2 for all Overo COMs Ash Charles
2015-06-12 20:37 ` [PATCH 4/5] omap3: overo: Support PoP NAND Ash Charles
     [not found] ` <1434141446-11568-1-git-send-email-ashcharles-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-06-12 20:37   ` [PATCH 5/5] omap3: overo: Add device tree for Palo35 board Ash Charles

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=1434141446-11568-2-git-send-email-ashcharles@gmail.com \
    --to=ashcharles@gmail.com \
    --cc=adam.yh.lee@gmail.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.com \
    /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