diff options
| author | Ajit Vaishya <ajitv@codeaurora.org> | 2020-01-09 22:45:35 +0530 |
|---|---|---|
| committer | Ajit Vaishya <ajitv@codeaurora.org> | 2020-01-21 22:20:57 +0530 |
| commit | 6b85faadc8f3dd72f9ea876fe71b61592b7902e1 (patch) | |
| tree | 969a8d1c68814b2383ae2fe70dd196e8087a8db9 /identity/support/src/cppbor_parse.cpp | |
| parent | 64eb56cc5e6bf80b8e9abe44da98eb8bf39370c3 (diff) | |
Move the iface down of nan vdev to NanIface invalidate.
Currently when user run three port concurrency from UI
i.e. 1) STA + NAN + SAP
2) STA + NAN + STA
the chip reconfiguration happens where the NAN disableRequest
is not triggered but the removeNanIface (invalidateAndClear)
gets triggered.Thus,the iface down of NAN vdev in the earlier
behavior through the commit "Use additional interface for the
NAN operations" does not help as the iface was done when the
NAN disableRequest is triggered.
Due to this Next NAN enable from UI fails.
Also, this invalidateAndClear ( Nan invalidate ) is called in
all the scenarios , say wifi->stop , nanDisableRequest from
the NAN Application (removeNanIface).
Thus , the commit moves the NAN iface down to NanIface's
invalidate to address all the scenarios.
Change-Id: Ibb4d912f919ad4f875168a64c43071b43730e241
CRs-Fixed: 2602212
Diffstat (limited to 'identity/support/src/cppbor_parse.cpp')
0 files changed, 0 insertions, 0 deletions