All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Neukum <oneukum@suse.de>
To: linux-pm@lists.osdl.org
Cc: Pavel Machek <pavel@suse.cz>,
	Amit Kucheria <amit.kucheria@nokia.com>,
	Matthew Garrett <mjg59@srcf.ucam.org>,
	ipw2100-devel@lists.sourceforge.net, ext Andi Kleen <ak@suse.de>,
	netdev@vger.kernel.org
Subject: Re: [linux-pm] [RFC] Runtime power management on	ipw2100
Date: Wed, 31 Jan 2007 14:12:05 +0100	[thread overview]
Message-ID: <200701311412.06213.oneukum@suse.de> (raw)
In-Reply-To: <20070131130447.GF19643@elf.ucw.cz>

Am Mittwoch, 31. Januar 2007 14:04 schrieb Pavel Machek:
> On Wed 2007-01-31 13:53:20, Amit Kucheria wrote:
> > On Wed, 2007-01-31 at 11:48 +0100, ext Andi Kleen wrote:
> > > On Wednesday 31 January 2007 11:27, Matthew Garrett wrote:
> > > > On Wed, Jan 31, 2007 at 12:13:04PM +0100, Andi Kleen wrote:
> > > > > 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)
> > > > 
> > > > Hm. How would this interact with receiving packets?
> > > 
> > > The hardware will hopefully have support to wake itself up when that 
> > > happens.
> > 
> > Yes. Low power states without ability to respond to wakeup interrupts
> > would be broken behaviour generally.
> 
> Do you realy expect wifi to save significant ammount of power, while
> still listening for packets on wireless network?

It has a managed mode which gives each station a timeslot. Outside
those slots you could power down, if you can do it quickly.

	Regards
		Oliver

  reply	other threads:[~2007-01-31 13:12 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               ` Oliver Neukum [this message]
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=200701311412.06213.oneukum@suse.de \
    --to=oneukum@suse.de \
    --cc=ak@suse.de \
    --cc=amit.kucheria@nokia.com \
    --cc=ipw2100-devel@lists.sourceforge.net \
    --cc=linux-pm@lists.osdl.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=netdev@vger.kernel.org \
    --cc=pavel@suse.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.