Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Sender: msinada=codeaurora.org@mg.codeaurora.org
DMARC-Filter: OpenDMARC Filter v1.4.1 smtp.codeaurora.org C4CD2C4338F
From:   "Muna Sinada" <msinada@codeaurora.org>
To:     "'Johannes Berg'" <johannes@sipsolutions.net>
Cc:     <linux-wireless@vger.kernel.org>
References: <1628660743-24413-1-git-send-email-msinada@codeaurora.org> <ec979481036ad198d4c42d2756caf66fd3496bbc.camel@sipsolutions.net>
In-Reply-To: <ec979481036ad198d4c42d2756caf66fd3496bbc.camel@sipsolutions.net>
Subject: RE: [PATCH v2] cfg80211: Handle driver updated MU-EDCA params
Date:   Thu, 26 Aug 2021 16:18:21 -0700
Message-ID: <001801d79ad0$a9a92a70$fcfb7f50$@codeaurora.org>
MIME-Version: 1.0
Content-Type: text/plain;
        charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Language: en-us
Thread-Index: AQKPi0h8Y3QBEVBPnfPFaPv7V44okgHUa8dSqgfksbA=
Precedence: bulk

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>=20
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=20
> parameters from driver and send to user space, where management frame=20
> are updated to reflect latest parameters.
>=20

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