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, Adrian Chadd wrote:
hi,
so it's going to eventually leak? Can we fix the firmware bug too? :)
-a
On 26 February 2018 at 09:06, <[email protected]> wrote:
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
request
from host driver. Firmware free the user_id in peer delete operation.
Regards,
Karthikeyan P.
_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k
