From: Andi Kleen <ak@suse.de>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: ipw2100-devel@lists.sourceforge.net, netdev@vger.kernel.org,
linux-pm@lists.osdl.org
Subject: Re: [RFC] Runtime power management on ipw2100
Date: 31 Jan 2007 12:13:04 +0100 [thread overview]
Message-ID: <p731wlbphz3.fsf@bingen.suse.de> (raw)
In-Reply-To: <20070131094858.GA23842@srcf.ucam.org>
Matthew Garrett <mjg59@srcf.ucam.org> writes:
>
> PCI seems to require a delay of 10ms when sequencing from D3 to D0,
> which probably isn't acceptable latency for an "up" state.
It might be if the interface has been idle for some time
(and the delay is not busy looping of course)
How idle should be user configurable.
But the idle detection needed for that should be probably higher
up stack or at least some common library functions.
-Andi
next prev parent reply other threads:[~2007-01-31 11:13 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 [this message]
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 ` [linux-pm] [Ipw2100-devel] " 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=p731wlbphz3.fsf@bingen.suse.de \
--to=ak@suse.de \
--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).