From: Christian Lamparter <chunkeey@googlemail.com>
To: Marco Porsch <marco@cozybit.com>
Cc: johannes@sipsolutions.net, mcgrof@qca.qualcomm.com,
jouni@qca.qualcomm.com, vthiagar@qca.qualcomm.com,
senthilb@qca.qualcomm.com, sleffler@google.com,
linux-wireless@vger.kernel.org, devel@lists.open80211s.org,
ath9k-devel@lists.ath9k.org
Subject: Re: [PATCHv2 2/3] mac80211: mesh power save doze scheduling
Date: Mon, 18 Feb 2013 17:41:03 +0100 [thread overview]
Message-ID: <201302181741.03279.chunkeey@googlemail.com> (raw)
In-Reply-To: <1361203709-16669-2-git-send-email-marco@cozybit.com>
On Monday, February 18, 2013 05:08:28 PM Marco Porsch wrote:
> ---
> +/**
> + * ieee80211_mps_sta_tbtt_update - update peer beacon wakeup schedule
> + *
> + * @sta: mesh STA
> + * @mgmt: beacon frame
> + * @tim: TIM IE of beacon frame
> + * @tsf_local: current HW TSF
> + */
> +void ieee80211_mps_sta_tbtt_update(struct sta_info *sta,
> + struct ieee80211_mgmt *mgmt,
> + const struct ieee80211_tim_ie *tim,
> + u64 tsf_local)
> +{
> + struct ieee80211_sub_if_data *sdata = sta->sdata;
> +
> + if (!sdata->local->mps_enabled ||
> + sta->plink_state != NL80211_PLINK_ESTAB)
> + return;
> +
> + sta->beacon_interval = le16_to_cpu(mgmt->u.beacon.beacon_int) * 1024;
If you want, you could use ieee80211_tu_to_usec instead of "* 1024":
sta->beacon_interval = ieee80211_tu_to_usec(le16_to_cpu(mgmt->u.beacon.beacon_int));
Regards,
Chr
next prev parent reply other threads:[~2013-02-18 16:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 16:08 [PATCHv2 1/3] mac80211: move mesh sync beacon handler into neighbour_update Marco Porsch
2013-02-18 16:08 ` [PATCHv2 2/3] mac80211: mesh power save doze scheduling Marco Porsch
2013-02-18 16:41 ` Christian Lamparter [this message]
2013-02-20 15:01 ` Johannes Berg
2013-02-25 10:06 ` Marco Porsch
2013-02-26 20:52 ` Johannes Berg
2013-02-18 16:08 ` [PATCHv2 3/3] ath9k: mesh powersave support Marco Porsch
2013-02-20 14:50 ` [PATCHv2 1/3] mac80211: move mesh sync beacon handler into neighbour_update Johannes Berg
2013-02-20 18:26 ` Thomas Pedersen
2013-02-20 20:00 ` Johannes Berg
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=201302181741.03279.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=devel@lists.open80211s.org \
--cc=johannes@sipsolutions.net \
--cc=jouni@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=marco@cozybit.com \
--cc=mcgrof@qca.qualcomm.com \
--cc=senthilb@qca.qualcomm.com \
--cc=sleffler@google.com \
--cc=vthiagar@qca.qualcomm.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).