From: Greg KH <greg@kroah.com>
To: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ordering of suspend/resume for devices. any clues, anyone?
Date: Thu, 15 Dec 2005 10:37:44 -0800 [thread overview]
Message-ID: <20051215183744.GB16574@kroah.com> (raw)
In-Reply-To: <20051215143124.GD14978@lkcl.net>
On Thu, Dec 15, 2005 at 02:31:24PM +0000, Luke Kenneth Casson Leighton wrote:
> [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.]
>
> http://handhelds.org/moin/moin.cgi/BlueAngel
>
> 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.
>
> of course - this can't be taken care of in userspace as an apm
> event because the framebuffer device cannot be a module [without
> terminating all running x-applications].
>
> so.
>
> possible solutions, as i see them:
<snip>
Known issue, I'd take this to the linux-pm mailing list instead, as the
people there are working on stuff for this.
thanks,
greg k-h
next prev parent reply other threads:[~2005-12-15 18:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-15 14:31 ordering of suspend/resume for devices. any clues, anyone? Luke Kenneth Casson Leighton
2005-12-15 18:37 ` Greg KH [this message]
2005-12-15 19:47 ` Luke Kenneth Casson Leighton
2005-12-21 10:21 ` Pavel Machek
2005-12-21 22:49 ` Luke Kenneth Casson Leighton
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=20051215183744.GB16574@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkcl@lkcl.net \
/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