From: Kalle Valo <kvalo@codeaurora.org>
To: Maxim Altshul <maxim.altshul@ti.com>
Cc: <linux-wireless@vger.kernel.org>, <johannes@sipsolutions.net>,
Maxim Altshul <maxim.altshul@ti.com>
Subject: Re: [2/3,v2] wlcore: Pass win_size taken from ieee80211_sta to FW
Date: Thu, 17 Nov 2016 06:39:11 +0000 (UTC) [thread overview]
Message-ID: <20161117063911.A1209615C4@smtp.codeaurora.org> (raw)
In-Reply-To: <20160821112425.11302-2-maxim.altshul@ti.com>
Maxim Altshul <maxim.altshul@ti.com> wrote:
> When starting a new BA session, we must pass the win_size to the FW.
>
> To do this we take max_rx_aggregation_subframes (BA RX win size)
> which is stored in ieee80211_sta structure (e.g per link and not per HW)
>
> We will use the value stored per link when passing the win_size to
> firmware through the ACX_BA_SESSION_RX_SETUP command.
>
> Signed-off-by: Maxim Altshul <maxim.altshul@ti.com>
2 patches applied to wireless-drivers-next.git, thanks.
42c7372a1116 wlcore: Pass win_size taken from ieee80211_sta to FW
e7ee74b56f23 wlcore: Add RX_BA_WIN_SIZE_CHANGE_EVENT event
--
https://patchwork.kernel.org/patch/9292121/
Documentation about submitting wireless patches and checking status
from patchwork:
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2016-11-17 6:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-21 11:24 [PATCH 1/3 v2] mac80211: RX BA support for sta max_rx_aggregation_subframes Maxim Altshul
2016-08-21 11:24 ` [PATCH 2/3 v2] wlcore: Pass win_size taken from ieee80211_sta to FW Maxim Altshul
2016-08-21 11:24 ` [PATCH 3/3 v2] wlcore: Add RX_BA_WIN_SIZE_CHANGE_EVENT event Maxim Altshul
2016-09-14 16:41 ` [2/3,v2] wlcore: Pass win_size taken from ieee80211_sta to FW Kalle Valo
2016-11-17 6:39 ` Kalle Valo [this message]
2016-08-22 13:37 ` [PATCH 1/3 v2] mac80211: RX BA support for sta max_rx_aggregation_subframes 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=20161117063911.A1209615C4@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=maxim.altshul@ti.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).