linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Daniel Morsing <daniel.morsing@gmail.com>
Cc: Thomas Weber <thomas.weber.linux@googlemail.com>,
	Tony Lindgren <tony@atomide.com>,
	Bryan Wu <bryan.wu@canonical.com>,
	"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 2/2] omap3: devkit8000: Add and use 4.3 inch display
Date: Fri, 18 Feb 2011 13:07:46 +0000	[thread overview]
Message-ID: <1298034466.24062.99.camel@deskari> (raw)
In-Reply-To: <1298033744.2323.9.camel@morsing>

On Fri, 2011-02-18 at 06:55 -0600, Daniel Morsing wrote:
> On Fri, 2011-02-18 at 13:36 +0100, Thomas Weber wrote:
> > Hello Daniel,
> > 
> > Am 12.02.2011 18:02, schrieb Daniel Morsing:
> > > This patch adds a generic panel entry for the 4.3 inch display that is
> > > sold with the devkit8000 and modifies the board file to use this
> > > display.
> > > 
> > > 
> > 
> > So only the 4.3 inch display can be used with the devkit8000?
> > There are also Devkit8000 with 5.6 and 7 inch displays.
> > 
> > Regards,
> > Thomas
> > 
> 
> Yeah, I'll admit that the patch is a bit one-sided. I couldn't find a
> way to specify a board using a class of displays with separate timing
> settings.
> 
> One way to do it would be to add the settings to modedb, but modedb is
> really only for standardized display settings. The other way to do it
> would be to add a kernel config for which display you have connected to
> the board, but I think that is a bad idea, because it makes everything
> more complicated and switching out displays would require recompiling
> the kernel.
> 
> Maybe Tomi or the fbdev guys have some input on how to best do this?

There's no proper way for this currently. And I'm not even sure what
would be a good way to do this.

Optimally the board code could read some configuration value from eeprom
or where-ever, which would tell the configuration of the board. And the
board file could then configure the correct display.

Another way would be to add a devkit8000 specific kernel parameter,
given from bootloader, which would tell the configuration. The board
file would use this parameter to configure the correct display.

 Tomi



  reply	other threads:[~2011-02-18 13:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-12 17:02 [PATCH 0/2] Add recommended bpp for omap dss2 generic dpi panels Daniel Morsing
2011-02-12 17:02 ` [PATCH 1/2] omap: dss2: Add recommended bpp option for " Daniel Morsing
2011-02-12 17:02 ` [PATCH 2/2] omap3: devkit8000: Add and use 4.3 inch display Daniel Morsing
2011-02-16 14:42   ` Thomas Weber
2011-02-18 12:36   ` Thomas Weber
2011-02-18 12:55     ` Daniel Morsing
2011-02-18 13:07       ` Tomi Valkeinen [this message]
2011-02-18 16:18         ` Daniel Morsing
2011-02-18 16:43           ` Tomi Valkeinen
2011-02-16 13:11 ` [PATCH 0/2] Add recommended bpp for omap dss2 generic dpi Tomi Valkeinen
2011-02-16 14:06   ` Daniel Morsing
2011-02-16 14:36     ` Tomi Valkeinen
2011-02-16 15:42       ` Daniel Morsing
2011-02-16 15:58         ` Tomi Valkeinen
2011-02-16 19:22           ` Daniel Morsing

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=1298034466.24062.99.camel@deskari \
    --to=tomi.valkeinen@ti.com \
    --cc=bryan.wu@canonical.com \
    --cc=daniel.morsing@gmail.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=thomas.weber.linux@googlemail.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).