From: Zhu Yi <yi.zhu@intel.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: ipw2100-devel@lists.sourceforge.net, linux-pm@lists.osdl.org,
netdev@vger.kernel.org
Subject: Re: [RFC] Runtime power management on ipw2100
Date: Thu, 08 Feb 2007 17:01:46 +0800 [thread overview]
Message-ID: <1170925306.19089.125.camel@debian.sh.intel.com> (raw)
In-Reply-To: <20070206214407.GA5254@srcf.ucam.org>
On Tue, 2007-02-06 at 21:44 +0000, Matthew Garrett wrote:
> I'm reluctant to drop the IRQ because PCMCIA seems to have
> a nasty habit of grabbing free looking IRQs and setting them to be
> edge triggered, which would obviously be bad.
Can you provide more details for this problem and why we should
workaround it here instead of fixing the PCMCIA driver (hardware)?
A generic requirement for dynamic power management is the hardware
resource should not be touched when you put it in a low power state. In
this case, ipw2100 interrupt handler is possibly called (for example, it
shares the same IRQ with other devies) and it touches the card register,
which will cause problem. A possible workaround is to check the suspend
state in the beginning of the ISR and returns IRQ_NONE. But I think
freeing the irq handler before suspend should be the right way to go.
Thanks,
-yi
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next prev parent reply other threads:[~2007-02-08 9:01 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 [this message]
2007-02-19 21:08 ` [linux-pm] " David Brownell
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=1170925306.19089.125.camel@debian.sh.intel.com \
--to=yi.zhu@intel.com \
--cc=ipw2100-devel@lists.sourceforge.net \
--cc=linux-pm@lists.osdl.org \
--cc=mjg59@srcf.ucam.org \
--cc=netdev@vger.kernel.org \
/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).