From: Andrew Lutomirski <andy@luto.us>
To: reinette chatre <reinette.chatre@intel.com>
Cc: "ilw@linux.intel.com" <ilw@linux.intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] iwlcore: Allow runtime configuration of no_sleep_autoadjust
Date: Mon, 9 Nov 2009 17:47:02 -0500 [thread overview]
Message-ID: <cb0375e10911091447y375c276emddc5eff38b4b575e@mail.gmail.com> (raw)
In-Reply-To: <1257805265.21134.22738.camel@rc-desk>
On Mon, Nov 9, 2009 at 5:21 PM, reinette chatre
<reinette.chatre@intel.com> wrote:
> Hi Andrew,
>
> On Mon, 2009-11-09 at 10:07 -0800, Andrew Lutomirski wrote:
>> Hmm. It looks like sleep_level_override in debugfs can do exactly what I want.
>
> You have not really stated what you are trying to do here so it is hard
> to tell. sleep_level_override lets you hardcode the power saving index.
>
>>
>> Is there any reason that no_sleep_autoadjust doesn't just make
>> sleep_level_override default to 1?
>
> That does seem what it is doing in iwl_power_update_mode().
I want to save power. no_sleep_autoadjust=N and iwconfig wlan0 power
on does a good job of that. I assume that no_sleep_autoadjust
defaults to Y because it's still not reliable (and I seem to have seen
a few networks where it causes occasional problems). So I'd like to
be able to toggle it at runtime, file bug reports when it fails, but
still be able to use the networks it fails on :)
--Andy
next prev parent reply other threads:[~2009-11-09 22:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-08 19:30 [PATCH] iwlcore: Allow runtime configuration of no_sleep_autoadjust Andrew Lutomirski
2009-11-09 17:19 ` reinette chatre
2009-11-09 18:07 ` Andrew Lutomirski
2009-11-09 22:21 ` reinette chatre
2009-11-09 22:47 ` Andrew Lutomirski [this message]
2009-11-09 23:01 ` 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=cb0375e10911091447y375c276emddc5eff38b4b575e@mail.gmail.com \
--to=andy@luto.us \
--cc=ilw@linux.intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=reinette.chatre@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