From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: Ian Molton <spyro@f2s.com>, adaplas@pol.net
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Fw: Initialisation sequencing.
Date: Fri, 4 Mar 2005 08:45:34 +0800 [thread overview]
Message-ID: <200503040845.36571.adaplas@hotpop.com> (raw)
In-Reply-To: <4227A5CE.4050008@f2s.com>
On Friday 04 March 2005 08:03, Ian Molton wrote:
> Antonino A. Daplas wrote:
> > Are you using the backlight architecture in drivers/video/backlight?
> > Shouldn't the backlight driver pull the video driver first? I think
> > you can do that if you make the backlight driver depend on the video
> > driver.
>
> IOW make it a child of it?
>
> I asumed that would work but I cant actually build a modular kernel for
> some reason I havent had time to look into yet.
>
> that said, does load order have *any* bearing on probe order ?
> since both devices are platform devices, both drivers can be loaded and
> dormant and brought up at any time by their devices becomming available
> from (another) module...
If you really need to ensure that video gets loaded before backlight, you can
insert:
module_get/try_module_get(<video_driver>) in your backlight on load,
module_put() on unload.
Tony
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-04 0:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 6:38 Fw: Initialisation sequencing Antonino A. Daplas
2005-03-03 9:18 ` Ian Molton
2005-03-03 20:07 ` Antonino A. Daplas
2005-03-04 0:03 ` Ian Molton
2005-03-04 0:45 ` Antonino A. Daplas [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-03 0:41 Andrew Morton
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=200503040845.36571.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=adaplas@pol.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=spyro@f2s.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).