public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@nokia.com>
To: "ext Enric Balletbò i Serra" <eballetbo@gmail.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Add new omap_dss_device after dss_device_registration
Date: Mon, 01 Nov 2010 16:53:05 +0200	[thread overview]
Message-ID: <1288623185.5614.50.camel@tubuntu> (raw)
In-Reply-To: <AANLkTi=ph99HPyzNunrjKZnQqrndghCV5DVTUizjNN9+@mail.gmail.com>

On Wed, 2010-10-27 at 13:39 +0200, ext Enric Balletbò i Serra wrote:
> Hello all,
> 
> Can I add a new omap_dss_device after dss_device registration  ?
> Something like add_new_omap_dss_device(lcd_device) or similar ?
> 
> On IGEP v2 we register only igep2_dvi_device as dss_device, We want to
> add a new dss_device (igep2_lcd_device) after dss registration. Is it
> possible ?
> 
> For example we want to do something like this :
> 
>   step 1: register IGEP v2  dss_devices (dvi)
>   step 2: detect if IGEP expansion board is detected.
>   step 3: if it's detected add new dss_devices (lcd)

Hmm... Not quite like that, I think.

I think you have to have both devices in the omap_dss_board_info, and
you have to have the drivers for both devices loaded when omapfb starts.

But you don't necessarily have to use the second driver, and you could
have its enable() fail if the expansion board is missing.

 Tomi


--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2010-11-01 14:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-27 11:39 Add new omap_dss_device after dss_device_registration Enric Balletbò i Serra
2010-11-01 14:53 ` Tomi Valkeinen [this message]

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=1288623185.5614.50.camel@tubuntu \
    --to=tomi.valkeinen@nokia.com \
    --cc=eballetbo@gmail.com \
    --cc=linux-omap@vger.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