From: "Franky Lin" <frankyl@broadcom.com>
To: "Dani Camps" <danicamps81@yahoo.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Forcing wi-fi chipset to sleep from bcm4329 driver
Date: Fri, 17 Aug 2012 10:38:37 -0700 [thread overview]
Message-ID: <502E819D.3000203@broadcom.com> (raw)
In-Reply-To: <1345187963.23828.YahooMailNeo@web29704.mail.ird.yahoo.com>
On 08/17/2012 12:19 AM, Dani Camps wrote
> I am working on a research project, and our intention is to study the effect that the Wi-Fi radio has on the battery life of an Android mobile phone. In particular we would like to be able to configure the wi-fi radio to stay "awake" for a certain time period and "sleeping" for other time periods, and then study how the length of these intervals affects battery lifetime. From your answer, I understand that we cannot control exactly the power state of the chipset, but I wanted to check with you whether the following approach might work:
>
> 0- We let the mobile device associate with an Access Point.
> 1- When we want the chipset to stay awake, we send from the driver a PM_OFF configuration command to the chipset. What I expect it would happen is that the chipset sends a packet to the AP with PM=0, and stays awake all the time.
> 2- When we want to send the chipset to sleep, we send from the driver a PM_MAX configuration command to the chipset. What I expect it would happen is that the chipset sends a packet to the AP with PM=1, and goes to sleep. Now, IF we can guarantee that there is no traffic to/from the mobile device during the time that we want the chipset to be sleep, then the chipset will indeed be sleeping *most* of the time. The only exception will be that the chipset will regularly wake up to catch a Beacon frame, but probably it is also possible to configure how often that happens, and thus the effect on our measurements is not large.
>
> Do you think the previous method is sound?
>
Your approach looks good. I think that's the best we can do. ;)
Franky
prev parent reply other threads:[~2012-08-17 17:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 11:08 Forcing wi-fi chipset to sleep from bcm4329 driver Dani Camps
2012-08-16 17:54 ` Franky Lin
2012-08-17 7:19 ` Dani Camps
2012-08-17 17:38 ` Franky Lin [this message]
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=502E819D.3000203@broadcom.com \
--to=frankyl@broadcom.com \
--cc=danicamps81@yahoo.com \
--cc=linux-wireless@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).