linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kalle.valo@iki.fi>
To: "Guy\, Wey-Yi W" <wey-yi.w.guy@intel.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	Dan Williams <dcbw@redhat.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Matthew Garrett <mjg@redhat.com>,
	Marcel Holtmann <marcel@holtmann.org>
Subject: Re: wireless powersaving (in NM?)
Date: Tue, 24 Mar 2009 17:03:24 +0200	[thread overview]
Message-ID: <8763hzq7yb.fsf@litku.valot.fi> (raw)
In-Reply-To: <E9954878DD1FB34FAE5187FB88C58A3546DA95D4@orsmsx506.amr.corp.intel.com> (Wey-Yi W. Guy's message of "Tue\, 24 Mar 2009 07\:47\:46 -0700")

"Guy, Wey-Yi W" <wey-yi.w.guy@intel.com> writes:

> Hi Johannes,

Hello,

> Especially for Netbook and Handle devices with newer processor.
> Putting system into lower C-state and having longer battery life is
> very important. I think letting driver making the default choice based
> on the power source is the right way to go, but always can be
> overwritten by upper layer (mac80211 or NM?).

You mean that the driver knows if the AC is connected or not?
Definitely not, the AC connection logic is a policy decision and needs
to be in userspace. It should not be in kernel, it would just
complicate the implementation.

> I do not think we need to expose all the power levels to user space;
> those should be internal decision (mac80211 or driver). User space can
> make the choice of turn power saving mode on/off and leave the detail
> decision to the lower layer which has better knowledge of how to
> balance the power and performance.

mac80211 or the driver doesn't have all the needed knowledge. For
example, how to enable more aggressive power save when the display is
off? The driver certainly doesn't (and shouldn't) know that.

-- 
Kalle Valo

  reply	other threads:[~2009-03-24 15:03 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-24 10:39 wireless powersaving (in NM?) Johannes Berg
2009-03-24 10:32 ` Marcel Holtmann
2009-03-25 10:45   ` Johannes Berg
2009-03-24 13:47 ` John W. Linville
2009-03-24 13:53 ` Johannes Berg
2009-03-24 14:47   ` Guy, Wey-Yi W
2009-03-24 15:03     ` Kalle Valo [this message]
2009-03-24 14:17 ` Kalle Valo
2009-03-25 10:57   ` Johannes Berg
2009-03-25 19:53     ` Kalle Valo
2009-03-25 20:06       ` Johannes Berg
2009-03-25 20:09         ` Johannes Berg
2009-03-25 20:22         ` Kalle Valo
2009-03-24 15:59 ` Dan Williams
2009-03-25 11:04   ` Johannes Berg
2009-03-25 15:31     ` Dan Williams
2009-03-25 15:48       ` Johannes Berg
2009-03-26  8:00         ` Luis R. Rodriguez
2009-03-26  8:11           ` Johannes Berg
2009-03-26  8:39             ` Luis R. Rodriguez
2009-03-26  8:54               ` Johannes Berg
2009-03-26  9:01                 ` Luis R. Rodriguez
2009-03-26 14:29                   ` Georgy Berdyshev
2009-03-26  8:19           ` Kalle Valo
2009-03-26  8:40             ` Luis R. Rodriguez
2009-03-31 16:28 ` Johannes Berg
2009-04-01 11:04 ` more thoughts on power saving (was: wireless powersaving (in NM?)) Johannes Berg
2009-04-01 11:12   ` Kalle Valo
2009-04-01 14:29     ` Guy, Wey-Yi W

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=8763hzq7yb.fsf@litku.valot.fi \
    --to=kalle.valo@iki.fi \
    --cc=dcbw@redhat.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=mjg@redhat.com \
    --cc=wey-yi.w.guy@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).