linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Helmut Schaa <helmut.schaa@googlemail.com>
To: reinette chatre <reinette.chatre@intel.com>
Cc: "linville@tuxdriver.com" <linville@tuxdriver.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"ipw3945-devel@lists.sourceforge.net"
	<ipw3945-devel@lists.sourceforge.net>,
	"Guy, Wey-Yi W" <wey-yi.w.guy@intel.com>
Subject: Re: [PATCH 2/3] iwlwifi: remove STATUS_ALIVE checking from rf_kill
Date: Fri, 27 Mar 2009 07:25:34 +0100	[thread overview]
Message-ID: <200903270725.35166.helmut.schaa@gmail.com> (raw)
In-Reply-To: <1238110011.10348.19.camel@rc-desk>

Hi,

Am Freitag, 27. M=C3=A4rz 2009 schrieb reinette chatre:
> On Thu, 2009-03-26 at 13:58 -0700, Helmut Schaa wrote:
> > Assume the following situation:
> >=20
> > You only have one killswitch for both, wireless and bluetooth. The =
wireless
> > interface is down because it is unused and the user wants to use bl=
uetooth
> > and enables it via the killswitch which also means that wireless ge=
ts
> > unkilled. Now restarting the adapter needs more power then keeping =
the
> > adapter down. In short: if the interface is down the user (space) d=
oes not
> > want to use the interface and probably wants to save power as well.
>=20
> Your measurements are very fine grained :) Will this be measureable?

Heh, you know the internals of the devive ;) but I guess waking up the
adapter (and thus starting the firmware) even if the interface is unuse=
d
will surely need more power than not doing so.

Helmut
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2009-03-27  6:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26 17:14 [PATCH 0/3] iwlwifi driver updates 03/26/2009 Reinette Chatre
2009-03-26 17:14 ` [PATCH 1/3] iwlwifi: merge and better support of suspend/resume for iwlagn and iwl3945 Reinette Chatre
2009-03-26 17:14   ` [PATCH 2/3] iwlwifi: remove STATUS_ALIVE checking from rf_kill Reinette Chatre
2009-03-26 17:14     ` [PATCH 3/3] iwl3945: use iwl_mac_conf_tx Reinette Chatre
2009-03-26 17:50     ` [PATCH 2/3] iwlwifi: remove STATUS_ALIVE checking from rf_kill Helmut Schaa
2009-03-26 18:22       ` reinette chatre
2009-03-26 19:11         ` Helmut Schaa
2009-03-26 19:30           ` reinette chatre
2009-03-26 19:49             ` Helmut Schaa
2009-03-26 20:37               ` reinette chatre
2009-03-26 20:58                 ` Helmut Schaa
2009-03-26 23:26                   ` reinette chatre
2009-03-27  6:19                     ` Helmut Schaa
2009-03-27  6:25                     ` Helmut Schaa [this message]
2009-03-27 15:45                       ` reinette chatre
2009-03-27  3:49                   ` reinette chatre
2009-03-27  6:18     ` Helmut Schaa
2009-03-27 16:03       ` reinette chatre
2009-03-27 16:30         ` reinette chatre

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=200903270725.35166.helmut.schaa@gmail.com \
    --to=helmut.schaa@googlemail.com \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=reinette.chatre@intel.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).