From: Kalle Valo <kalle.valo@iki.fi>
To: Christian Lamparter <chunkeey@web.de>
Cc: Vivek Natarajan <Vivek.Natarajan@atheros.com>,
Johannes Berg <johannes@sipsolutions.net>,
"linux-wireless" <linux-wireless@vger.kernel.org>
Subject: Re: multicast traffic and ath9k
Date: Fri, 09 Jan 2009 19:33:40 +0200 [thread overview]
Message-ID: <874p08tmdn.fsf@litku.valot.fi> (raw)
In-Reply-To: <200901091713.12777.chunkeey@web.de> (Christian Lamparter's message of "Fri\, 9 Jan 2009 17\:13\:12 +0100")
Christian Lamparter <chunkeey@web.de> writes:
>> How does the mac80211 know if the hw is receiving mc traffic or not and
>> unset the CONF_PS flag accordingly? Am I missing something basic here?
>>
>> Maybe p54 (stlc45xx) has the answer for how it goes back to sleep
>> after mc traffic.
>
> Well we have a flag to tell the firmware to do the following thing
> in client mode (while sleeping)
>
> "If the PSM object's *_PSM_MCBC flag is set, and a beacon is
> received with the TIM's multicast traffic bit set, [...] or the LMAC
> stays awake until the TIM's multicast traffic bit is cleared again
> from the beacon".
I doubt that LMAC stays awake until next beacon arrives, that would
increase the power consumption too much. Most probably it follows the
more data from the multicast frames and goes to sleep immeaditely
after it has received the last multicast frame.
--
Kalle Valo
next prev parent reply other threads:[~2009-01-09 17:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 16:36 multicast traffic and ath9k Johannes Berg
2009-01-09 11:50 ` Vivek Natarajan
2009-01-09 11:57 ` Johannes Berg
2009-01-09 12:56 ` Vivek Natarajan
2009-01-09 13:07 ` Johannes Berg
2009-01-09 13:59 ` Vivek Natarajan
2009-01-09 16:13 ` Christian Lamparter
2009-01-09 17:33 ` Kalle Valo [this message]
2009-01-09 16:37 ` 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=874p08tmdn.fsf@litku.valot.fi \
--to=kalle.valo@iki.fi \
--cc=Vivek.Natarajan@atheros.com \
--cc=chunkeey@web.de \
--cc=johannes@sipsolutions.net \
--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).