From: Kalle Valo <kvalo@qca.qualcomm.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH 3/3] ath10k: enable STA UAPSD support
Date: Thu, 9 May 2013 10:17:28 +0300 [thread overview]
Message-ID: <8738twy647.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1367999363-20424-4-git-send-email-janusz.dziedzic@tieto.com> (Janusz Dziedzic's message of "Wed, 8 May 2013 09:49:23 +0200")
Janusz Dziedzic <janusz.dziedzic@tieto.com> writes:
> Enable UAPSD support for STA mode.
>
> Signed-off-by: Janusz Dziedzic <janusz.dziedzic@tieto.com>
Same here, please explain briefly what you have tested.
> --- a/drivers/net/wireless/ath/ath10k/mac.c
> +++ b/drivers/net/wireless/ath/ath10k/mac.c
> @@ -2296,6 +2296,68 @@ static int ath10k_sta_state(struct ieee80211_hw *hw,
> return ret;
> }
>
> +#define SET_UAPSD(enable, out, flags) do { \
> + if ((enable)) \
> + (out) |= (flags); \
> + else \
> + (out) &= ~(flags); \
> +} while (0)
Why the macro? To workaround a long line warning from checkpatch?
If that's a problem we could increate line length limit, for example to
85 or 90. In some cases the 80 char limit is a bit too excessive. Would
that help?
[...]
> + if (ret) {
> + ath10k_warn("could not set uapsd params (%d)\n", ret);
"could not set uapsd params: %d\n"
> + goto exit;
> + }
> +
> + if (arvif->u.sta.uapsd)
> + value = WMI_STA_PS_RX_WAKE_POLICY_POLL_UAPSD;
> + else
> + value = WMI_STA_PS_RX_WAKE_POLICY_WAKE;
> +
> + ret = ath10k_wmi_set_sta_ps_param(ar, arvif->vdev_id,
> + WMI_STA_PS_PARAM_RX_WAKE_POLICY,
> + value);
> + if (ret)
> + ath10k_warn("could not set rx wake param (%d)\n", ret);
> +exit:
> + return ret;
> +}
Empty line before the exit label.
> @@ -2335,13 +2399,20 @@ static int ath10k_conf_tx(struct ieee80211_hw *hw,
> */
> p->txop = params->txop * 32;
>
> - /* FIXME: can we pass the params->uapsd to the FW? */
> +
This now has two empty lines, one is enough.
> - if (ret)
> + if (ret) {
> ath10k_warn("could not set wmm params (%d)\n", ret);
> + goto exit;
> + }
The same comment as with the other warning message above.
> + ret = ath10k_conf_tx_uapsd(ar, vif, ac, params->uapsd);
> + if (ret)
> + ath10k_warn("could not set sta uapsd (%d)\n", ret);
Ditto.
--
Kalle Valo
next prev parent reply other threads:[~2013-05-09 7:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 7:49 [ath9k-devel] [PATCH 0/3] UAPSD support for STA/AP mode Janusz Dziedzic
2013-05-08 7:49 ` [ath9k-devel] [PATCH 1/3] ath10k: WMI add AP PS Janusz Dziedzic
2013-05-09 7:09 ` Kalle Valo
2013-05-09 7:35 ` Janusz.Dziedzic at tieto.com
2013-05-09 8:31 ` Kalle Valo
2013-05-08 7:49 ` [ath9k-devel] [PATCH 2/3] ath10k: add AP UAPSD support Janusz Dziedzic
2013-05-09 7:11 ` Kalle Valo
2013-05-08 7:49 ` [ath9k-devel] [PATCH 3/3] ath10k: enable STA " Janusz Dziedzic
2013-05-09 7:17 ` Kalle Valo [this message]
2013-05-09 7:47 ` Janusz.Dziedzic at tieto.com
2013-05-09 8:07 ` Michal Kazior
2013-05-09 8:47 ` Kalle Valo
2013-05-09 9:12 ` [ath9k-devel] [PATCH 0/3] UAPSD support for STA/AP mode Janusz.Dziedzic at tieto.com
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=8738twy647.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath9k-devel@lists.ath9k.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