From: Kalle Valo <kalle.valo@nokia.com>
To: "Vivek Natarajan" <vivek.natraj@gmail.com>
Cc: "Johannes Berg" <johannes@sipsolutions.net>,
"Vivek Natarajan" <vnatarajan@atheros.com>,
linux-wireless@vger.kernel.org
Subject: Re: [RFC] mac80211: Enhancements to dynamic power save.
Date: Mon, 01 Dec 2008 17:55:38 +0200 [thread overview]
Message-ID: <87oczv6gat.fsf@nokia.com> (raw)
In-Reply-To: <8e92b4100812010708r78aab0fdt9cb101df97fcc29@mail.gmail.com> (ext Vivek Natarajan's message of "Mon\, 1 Dec 2008 20\:38\:33 +0530")
Vivek Natarajan <vivek.natraj@gmail.com> writes:
>> One thing I forgot, do we need a special iwlwifi flag to turn this off?
Or a flag to turn it on? Either of them are fine, I guess.
> Kalle added a flag 'IEEE80211_HW_NO_DYNAMIC_PS' in v3 RFC.
> May be, it can be used for iwlwifi to use its own power save and
> null frames as it does now instead of using from mac80211.
> We can check this flag and then change CONF_PS wherever it is used.
I think we should have a separate hw flag for null frames.
--
Kalle Valo
next prev parent reply other threads:[~2008-12-01 15:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 1:17 [RFC] mac80211: Enhancements to dynamic power save Vivek Natarajan
2008-12-01 11:53 ` Johannes Berg
2008-12-01 15:08 ` Vivek Natarajan
2008-12-01 15:55 ` Kalle Valo [this message]
2008-12-01 15:52 ` Kalle Valo
2008-12-01 23:53 ` Luis R. Rodriguez
2008-12-01 12:05 ` Johannes Berg
2008-12-01 16:17 ` Kalle Valo
2008-12-01 17:00 ` Tomas Winkler
2008-12-02 12:58 ` Vivek Natarajan
2008-12-02 14:29 ` Tomas Winkler
2008-12-01 15:42 ` Kalle Valo
-- strict thread matches above, loose matches on Subject: below --
2008-12-23 4:44 Vivek Natarajan
2008-12-22 17:12 ` Johannes Berg
2008-12-23 12:50 ` Vivek Natarajan
2008-12-23 20:33 ` Kalle Valo
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=87oczv6gat.fsf@nokia.com \
--to=kalle.valo@nokia.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=vivek.natraj@gmail.com \
--cc=vnatarajan@atheros.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).