From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath10k: fix SMPS support
Date: Thu, 13 Feb 2014 16:29:29 +0200 [thread overview]
Message-ID: <87eh379jcm.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1391673591-8907-1-git-send-email-michal.kazior@tieto.com> (Michal Kazior's message of "Thu, 6 Feb 2014 08:59:51 +0100")
Michal Kazior <michal.kazior@tieto.com> writes:
> Firmware ignores SMPS flags in peer assoc command.
>
> For SMPS to work it is necessary to set peer
> parameter after peer assoc command so that tx
> chainmask is setup properly.
>
> This should fix packet loss and improve throughput
> with stations that have SMPS enabled upon
> association.
>
> Signed-off-by: Michal Kazior <michal.kazior@tieto.com>
[...]
> +static const u32 ath10k_smps_map[] = {
> + [WLAN_HT_CAP_SM_PS_STATIC] = WMI_PEER_SMPS_STATIC,
> + [WLAN_HT_CAP_SM_PS_DYNAMIC] = WMI_PEER_SMPS_DYNAMIC,
> + [WLAN_HT_CAP_SM_PS_INVALID] = WMI_PEER_SMPS_PS_NONE,
> + [WLAN_HT_CAP_SM_PS_DISABLED] = WMI_PEER_SMPS_PS_NONE,
> +};
> +
> +static int ath10k_setup_peer_smps(struct ath10k *ar, struct ath10k_vif *arvif,
> + const u8 *addr,
> + const struct ieee80211_sta_ht_cap *ht_cap)
> +{
> + int smps;
> +
> + if (!ht_cap->ht_supported)
> + return 0;
> +
> + smps = ht_cap->cap & IEEE80211_HT_CAP_SM_PS;
> + smps >>= IEEE80211_HT_CAP_SM_PS_SHIFT;
> +
> + if (smps >= ARRAY_SIZE(ath10k_smps_map))
> + return -EINVAL;
> +
> + return ath10k_wmi_peer_set_param(ar, arvif->vdev_id, addr,
> + WMI_PEER_SMPS_STATE,
> + ath10k_smps_map[smps]);
> +}
ath10k_smps_map looks overkill (and fragile), wouldn't a switch
statement be simpler?
> @@ -1370,6 +1385,7 @@ static void ath10k_bss_assoc(struct ieee80211_hw *hw,
> {
> struct ath10k *ar = hw->priv;
> struct ath10k_vif *arvif = ath10k_vif_to_arvif(vif);
> + struct ieee80211_sta_ht_cap ht_cap;
> struct wmi_peer_assoc_complete_arg peer_arg;
> struct ieee80211_sta *ap_sta;
> int ret;
> @@ -1386,6 +1402,8 @@ static void ath10k_bss_assoc(struct ieee80211_hw *hw,
> return;
> }
>
> + ht_cap = ap_sta->ht_cap;
Why do you copy ht_cap? I can't figure out the reason.
--
Kalle Valo
next prev parent reply other threads:[~2014-02-13 14:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 7:59 [PATCH] ath10k: fix SMPS support Michal Kazior
2014-02-13 14:29 ` Kalle Valo [this message]
2014-02-13 14:47 ` Michal Kazior
2014-02-13 15:20 ` Kalle Valo
2014-02-14 13:45 ` [PATCH v2] " Michal Kazior
2014-02-15 6:48 ` 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=87eh379jcm.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.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).