Hi,
This is not a bug, Firmware treats every WMI_PEER_ASSOC_CMDID as a new
peer assoc. so driver should not give WMI_PEER_ASSOC_CMDID for the
already associated peer.
For the NSS update, wmi_peer_set_param is enough to update the new NSS
value.
Regards,
Karthikeyan P.
On 2018-02-27 00:51, A
Hi,
Can you share exactly which resource the firmware ran out of? It would
seem to
be a FW bug if it is leaking, so maybe it can be fixed as well...
Firmware have total user_id = 528 (512 clients + 16 VAPs). Each user_id
is allocated to peer when Firmware receive the WMI_PEER_ASSOC_CMDID
On 2018-02-26 14:15, Adrian Chadd wrote:
hi!
On 25 February 2018 at 22:16, Karthikeyan Periyasamy
wrote:
This reverts commit 55884c045d31a29cf69db8332d1064a1b61dd159.
When Ath10k is in AP mode and an unassociated STA sends a VHT action
frame
(Operating Mode Notification for the NSS change) p
