[lkml]   [2005]   [Dec]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: ordering of suspend/resume for devices. any clues, anyone?
heya pavel,

thanks for the tip. as it turns out, a function table was hacked-n
that back-link from the w100fb framebuffer resume function into the
LCD code.

in this way, it is possible to call functions in the LCD module
doing GPIO to start the power-up sequence required for the
LCD and backlight, wait a few ms, initialise the video chip
(in the w100fb code), then call _another_ set of functions in
the LCD module to finish off the initialisation.

not pretty, but there you go.


On Wed, Dec 21, 2005 at 11:21:09AM +0100, Pavel Machek wrote:
> Hi!
> > [hi, please kindly cc me direct as i am deliberately subscribed with
> > settings to not receive posts from this list, but if that is inconvenient
> > for you to cc me, don't worry i can always look up the archives
> > to keep track of replies, thank you.]
> >
> >
> >
> > works.
> >
> > am seeking some advice regarding power management - specifically
> > the ordering of devices "resume" functions being called.
> >
> > we have an LCD, and an ATI chip. switching on the LCD powers up
> > the ATI chip.
> >
> > unfortunately, resume calls the ATI device initialisation
> > _before_ the LCD resume initialisation. the ATI chip's
> > initialisation fails - naturally - because it's not even
> > powered up.
> I'd say "make LCD system/platform device". That will init it first,
> shut it down last.
> Pavel
> --
> Thanks, Sharp!

<a href=""></a>
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-12-21 23:53    [W:0.064 / U:0.840 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site