From: David Brownell <david-b@pacbell.net>
To: linux-pm@lists.osdl.org
Cc: Zhu Yi <yi.zhu@intel.com>, Matthew Garrett <mjg59@srcf.ucam.org>,
ipw2100-devel@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: [linux-pm] [Ipw2100-devel] [RFC] Runtime power management on ipw2100
Date: Mon, 19 Feb 2007 13:08:49 -0800 [thread overview]
Message-ID: <200702191308.49797.david-b@pacbell.net> (raw)
In-Reply-To: <1170925306.19089.125.camel@debian.sh.intel.com>
On Thursday 08 February 2007 1:01 am, Zhu Yi wrote:
> A generic requirement for dynamic power management is the hardware
> resource should not be touched when you put it in a low power state.
That is in no way a "generic" requirement. It might apply specifically
to one ipw2100 low power state ... but "in general" devices may support
more than one low power state, with different levels of functionality.
Not all of those levels necessarily disallow touching the hardware.
> But I think
> freeing the irq handler before suspend should be the right way to go.
Some folk like that model a lot for shared IRQs. It shouldn't
matter for non-sharable ones.
- Dave
prev parent reply other threads:[~2007-02-19 21:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 7:52 [RFC] Runtime power management on ipw2100 Matthew Garrett
2007-01-31 9:13 ` Amit Kucheria
2007-01-31 9:48 ` [linux-pm] " Matthew Garrett
2007-01-31 11:04 ` Amit Kucheria
2007-01-31 11:13 ` Andi Kleen
2007-01-31 10:27 ` [linux-pm] " Matthew Garrett
2007-01-31 10:48 ` Andi Kleen
2007-01-31 11:53 ` Amit Kucheria
2007-01-31 13:04 ` Pavel Machek
2007-01-31 13:12 ` [linux-pm] " Oliver Neukum
2007-01-31 13:13 ` samuel
2007-01-31 13:24 ` Amit Kucheria
2007-01-31 13:44 ` [linux-pm] " Pavel Machek
2007-01-31 14:11 ` Matthew Garrett
2007-01-31 10:39 ` Pavel Machek
2007-02-01 1:47 ` [Ipw2100-devel] " Zhu Yi
2007-02-06 21:44 ` Matthew Garrett
2007-02-08 9:01 ` Zhu Yi
2007-02-19 21:08 ` David Brownell [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=200702191308.49797.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=ipw2100-devel@lists.sourceforge.net \
--cc=linux-pm@lists.osdl.org \
--cc=mjg59@srcf.ucam.org \
--cc=netdev@vger.kernel.org \
--cc=yi.zhu@intel.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).