In the current implementation, NAN enable and disable request are processed asynchronously, because of which some race conditions are seen. Example: If NDI is having multiple NDPs and without terminating NDPs if NAN disable and NDI delete are issued back to back then, NDP_END sequence is not initiated and causing deviation from NAN spec. Root-cause is firmware deleting NDP peer as a part of NDI delete before initiating NDP end sequence. To fix this, process NAN enable and disable requests synchronously. Change-Id: I467419370187b0dc8d879e1806347c9f21ebb23a CRs-Fixed: 2528599 |
||
---|---|---|
.. | ||
core | ||
dispatcher |