linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Archit Taneja <archit@ti.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 06/21] ARM: OMAP: overo: use new display drivers
Date: Tue, 30 Jul 2013 11:51:30 +0530	[thread overview]
Message-ID: <51F75B6A.6090900@ti.com> (raw)
In-Reply-To: <1374822504-28949-7-git-send-email-tomi.valkeinen@ti.com>

Hi,

On Friday 26 July 2013 12:38 PM, Tomi Valkeinen wrote:
> Use the new display drivers for OMAP3 Overo board.
>
> The new OMAP display drivers were merged for 3.11, and we can now change
> the board files to use the new ones and phase out the old ones.
>
> Note that the LCD add-on boards for lcd43 and lcd35 use the same GPIOs
> for the panels. This means that both panel devices cannot be probed at
> the same time.
>
> DT will handle this correctly, i.e. the DT data will contain the panel
> device only for the add-on board that is attached. However, for the
> board file we need a hackish solution: We parse the kernel boot command
> line, and see whether lcd43 or lcd35 is set as a default display, and
> add the given one. Or, if neither is given, default to lcd43.
>

<snip>

>   static struct omap_dss_board_info overo_dss_data = {
> -	.num_devices	= ARRAY_SIZE(overo_dss_devices),
> -	.devices	= overo_dss_devices,
> -	.default_device	= &overo_dvi_device,
> +	.default_display_name = "lcd43",
>   };

The default display previously was the dvi device, if both lcd43 and 
lcd35 are on add-on boards, then we should probably stick to dvi itself, 
right? The hack won't work if dvi is the default device though.

Archit


  reply	other threads:[~2013-07-30  6:22 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-26  7:08 [PATCH 00/21] ARM: OMAP2+: use new display drivers Tomi Valkeinen
2013-07-26  7:08 ` [PATCH 01/21] ARM: OMAP: dss-common: fix Panda's DVI DDC channel Tomi Valkeinen
2013-07-26  7:08 ` [PATCH 02/21] ARM: OMAP2+: Remove legacy DSS initialization for omap4 Tomi Valkeinen
2013-07-26  7:08 ` [PATCH 03/21] ARM: OMAP2+: Add selected display drivers to omap2plus_defconfig Tomi Valkeinen
2013-07-26  7:08 ` [PATCH 04/21] ARM: OMAP: dss-common: use new display drivers Tomi Valkeinen
2013-07-26  7:08 ` [PATCH 05/21] ARM: OMAP: 4430SDP: remove picodlp device data Tomi Valkeinen
2013-07-26  7:08 ` [PATCH 06/21] ARM: OMAP: overo: use new display drivers Tomi Valkeinen
2013-07-30  6:21   ` Archit Taneja [this message]
2013-07-30  6:39     ` Tomi Valkeinen
2013-07-30  7:07       ` Archit Taneja
2013-07-26  7:08 ` [PATCH 07/21] ARM: OMAP: rx51: " Tomi Valkeinen
2013-07-26  7:08 ` [PATCH 08/21] ARM: OMAP: beagle: " Tomi Valkeinen
2013-07-26  7:08 ` [PATCH 09/21] ARM: OMAP: devkit8000: " Tomi Valkeinen
2013-07-30  5:48   ` Archit Taneja
2013-07-30  6:01     ` Tomi Valkeinen
2013-07-26  7:08 ` [PATCH 10/21] ARM: OMAP: 2430SDP: " Tomi Valkeinen
2013-07-26  7:08 ` [PATCH 11/21] ARM: OMAP: LDP: " Tomi Valkeinen
2013-07-26  7:08 ` [PATCH 12/21] ARM: OMAP: omap3stalker: " Tomi Valkeinen
2013-07-26  7:08 ` [PATCH 13/21] ARM: OMAP: igep0020: " Tomi Valkeinen
2013-07-26  7:08 ` [PATCH 14/21] ARM: OMAP: cm-t35: " Tomi Valkeinen
2013-07-26  7:08 ` [PATCH 15/21] ARM: OMAP: H4: " Tomi Valkeinen
2013-07-26  7:08 ` [PATCH 16/21] ARM: OMAP: 3430SDP: " Tomi Valkeinen
2013-07-26  7:08 ` [PATCH 17/21] ARM: OMAP: OMAP3EVM: " Tomi Valkeinen
2013-07-26  7:08 ` [PATCH 18/21] ARM: OMAP: Pandora: " Tomi Valkeinen
2013-07-26  7:08 ` [PATCH 19/21] ARM: OMAP: Zoom: " Tomi Valkeinen
2013-07-26  7:08 ` [PATCH 20/21] ARM: OMAP: AM3517EVM: " Tomi Valkeinen
2013-07-26  7:08 ` [PATCH 21/21] ARM: OMAP2+: Remove old display drivers from omap2plus_defconfig Tomi Valkeinen
2013-08-09 10:53 ` [PATCH 00/21] ARM: OMAP2+: use new display drivers Tomi Valkeinen
2013-08-27  9:20   ` Tomi Valkeinen
2013-08-28  4:44     ` Tony Lindgren

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=51F75B6A.6090900@ti.com \
    --to=archit@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tomi.valkeinen@ti.com \
    --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;
as well as URLs for NNTP newsgroup(s).