From: Greg KH <greg@kroah.com>
To: Todd Poynor <tpoynor@mvista.com>
Cc: mochel@digitalimplant.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Leave runtime suspended devices off at system resume
Date: Fri, 28 May 2004 10:03:15 -0700 [thread overview]
Message-ID: <20040528170315.GB8192@kroah.com> (raw)
In-Reply-To: <20040526214319.GB7176@slurryseal.ddns.mvista.com>
On Wed, May 26, 2004 at 02:43:19PM -0700, Todd Poynor wrote:
> Currently all devices are resumed at system resume time, including any
> that were individually powered off ("at runtime") prior to the system
> suspend. In certain cases it can be nice to force back on individually
> suspended devices, such as the display, but hopefully this policy can be
> left up to userspace power managers; the kernel should probably honor
> the settings previously made by userspace/drivers. This seems
> preferable to requiring a power-conscious system to re-suspend devices
> after a system resume; furthermore, for certain platforms (such as
> XScale PXA27X) there can be disastrous consequences of powering up
> devices when the system is in a state incompatible with operation of the
> device.
>
> Suggested patch does this:
>
> (1) At system resume, checks power_state to see if the device was
> suspended prior to system suspend, and skips powering on the device if
> so.
>
> (2) Does not re-suspend an already-suspended device at system suspend
> (using a different method than is currently employed, which reorders the
> list, see #3).
>
> (3) Preserves the active/off device list order despite the above changes
> to suspend/resume behavior, to avoid dependency problems that tend to
> occur when the list is reordered.
Nice, that looks good.
Applied, thanks.
greg k-h
next prev parent reply other threads:[~2004-05-28 17:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-26 21:43 Todd Poynor
2004-05-28 17:03 ` Greg KH [this message]
2004-05-28 17:52 ` Todd Poynor
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=20040528170315.GB8192@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.org \
--cc=tpoynor@mvista.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
all inboxes | Powered by JetHome®