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@xxxxxxxxxxxxxxxx> Sent: Tuesday, August 17, 2021 6:54 AM To: Muna Sinada <msinada@xxxxxxxxxxxxxx> Cc: linux-wireless@xxxxxxxxxxxxxxx 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
