From: David Mosberger-Tang <davidm@egauge.net>
To: Ajay.Kathat@microchip.com
Cc: Claudiu.Beznea@microchip.com, kvalo@codeaurora.org,
davem@davemloft.net, kuba@kernel.org,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] wilc1000: Allow setting power_save before driver is initialized
Date: Wed, 15 Dec 2021 22:37:47 -0700 [thread overview]
Message-ID: <31d5e7447e4574d0fcfc46019d7ca96a3db4ecb6.camel@egauge.net> (raw)
In-Reply-To: <5378e756-8173-4c63-1f0d-e5836b235a48@microchip.com>
On Wed, 2021-12-15 at 13:01 +0000, Ajay.Kathat@microchip.com wrote:
> On 13/12/21 02:50, David Mosberger-Tang wrote:
> > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> >
> > Unfortunately, this patch doesn't seem to be sufficient. From what I
> > can tell, if power-save mode is turned on before a station is
> > associated with an access-point, there is no actual power savings. If
> > I issue the command after the station is associated, it works perfectly
> > fine.
> >
> > Ajay, does this make sense to you?
> <snip>
> Power-save mode is allowed to be enabled irrespective of station
> association state. Before association, the power consumption should be
> less with PSM enabled compared to PSM disabled. The WLAN automatic power
> save delivery gets enabled after the association with AP.
>
> To check the power measurement before association, test without
> wpa_supplicant.
>
>
> Steps:
> - load the module
> - ifconfig wlan0 up
> - iw dev wlan0 set power_save off (check the pwr measurement after PS
> mode disabled)
> - iw dev wlan0 set power_save on (check the pwr measurement after PS
> mode enable)
It appears wpa_supplicant consistently renders PSM ineffective:
(current draw, 1 min avg):
------------------------------ --------------------------
- base case (no module loaded): 16.8 mA
- module loaded & PSM on : 16.8 mA
- wpa_supplicant started : 19.6 mA
- PSM on : 19.6 mA (no change)
- PSM off : 19.6 mA (no change)
- PSM on : 15.4 mA
What's strange is when I try this sequence a couple of times in a row,
the device gets into a state where after starting wpa_supplicant, no
amount of PSM on/off commands will get it to enter power-savings mode
any more. When in that state, only removing wilc1000-spi.ko and adding
it back gets it out of that state. A power-cycle does not. Very
confusing.
--david
next prev parent reply other threads:[~2021-12-16 5:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-12 1:18 David Mosberger-Tang
2021-12-12 21:20 ` David Mosberger-Tang
2021-12-15 13:01 ` Ajay.Kathat
2021-12-16 5:37 ` David Mosberger-Tang [this message]
[not found] ` <49a5456d-6a63-652e-d356-9678f6a9b266@microchip.com>
2021-12-16 15:30 ` David Mosberger-Tang
2021-12-23 14:02 ` Ajay.Kathat
2021-12-23 17:08 ` David Mosberger-Tang
2021-12-24 16:20 ` Ajay.Kathat
2021-12-24 17:38 ` David Mosberger-Tang
[not found] ` <f961481a-3f4c-5fd2-c46a-037d923fea4c@microchip.com>
2022-01-04 6:07 ` David Mosberger-Tang
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=31d5e7447e4574d0fcfc46019d7ca96a3db4ecb6.camel@egauge.net \
--to=davidm@egauge.net \
--cc=Ajay.Kathat@microchip.com \
--cc=Claudiu.Beznea@microchip.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.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
all inboxes | Powered by JetHome®