From: "Muna Sinada" <msinada@codeaurora.org>
To: "'Johannes Berg'" <johannes@sipsolutions.net>
Cc: <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH v2] cfg80211: Handle driver updated MU-EDCA params
Date: Thu, 26 Aug 2021 16:18:21 -0700 [thread overview]
Message-ID: <001801d79ad0$a9a92a70$fcfb7f50$@codeaurora.org> (raw)
In-Reply-To: <ec979481036ad198d4c42d2756caf66fd3496bbc.camel@sipsolutions.net>
Hello Johannes,
The firmware algorithm determines better MU-EDCA parameters based on channel conditions. The updated parameters are used and reported to Hostapd to reflect in AP beacons. These dynamic parameter updates are offloaded to firmware for better user experience, and this would also mean that there are hardly any details on specifically how these parameters are determined but we know that the updated parameters need to be reflected in future beacons. This feature is meant for AP mode, and it is a ath11k feature, thus no spec references.
Thank you,
Muna
-----Original Message-----
From: Johannes Berg <johannes@sipsolutions.net>
Sent: Tuesday, August 17, 2021 6:54 AM
To: Muna Sinada <msinada@codeaurora.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] cfg80211: Handle driver updated MU-EDCA params
On Tue, 2021-08-10 at 22:45 -0700, Muna Sinada wrote:
> Add necessary functions and attributes to receive updated MU-EDCA
> parameters from driver and send to user space, where management frame
> are updated to reflect latest parameters.
>
On second thought - this really could use some more explanation?
Why are MU-EDCA parameters determined by the driver? What does this actually do? Is it meant for AP mode, or client mode? Any spec references?
Mac80211 parses this coming from the AP, so probably this is meant for AP mode, but why? Why wouldn't hostapd determine the correct parameters?
etc.
johannes
prev parent reply other threads:[~2021-08-26 23:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 5:45 [PATCH v2] cfg80211: Handle driver updated MU-EDCA params Muna Sinada
2021-08-17 13:54 ` Johannes Berg
2021-08-26 23:18 ` Muna Sinada [this message]
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='001801d79ad0$a9a92a70$fcfb7f50$@codeaurora.org' \
--to=msinada@codeaurora.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.