qcacld-3.0: Send NDI del rsp in NAN_DATA_DISCONNECTED_STATE state

NDI delete response is sent to userspace only when NDI is in
NAN_DATA_NDI_DELETING_STATE state. But NDI could be in
NAN_DATA_DISCONNECTED_STATE state if cleanup happens through
NDP_END_ALL path. Driver doesn't send response to userspace in
this case.
Send the response to userspace in NAN_DATA_DISCONNECTED_STATE also
as the application might be waiting for NDI delete status.
Also, use set/get APIs and avoid accessing NDI state directly.

Change-Id: I81a6b19a77144c76dde145f126c45b2ca67ff093
CRs-Fixed: 2679581
This commit is contained in:
Srinivas Dasari
2020-05-07 21:28:50 +05:30
committed by nshrivas
parent 50678287db
commit 632c058365
3 changed files with 23 additions and 15 deletions

View File

@@ -27,15 +27,20 @@
#include "nan_public_structs.h"
#ifdef WLAN_FEATURE_NAN
#define ucfg_nan_set_ndi_state(vdev, state) \
__ucfg_nan_set_ndi_state(vdev, state, __func__)
/**
* ucfg_nan_set_ndi_state: set ndi state
* @vdev: pointer to vdev object
* @state: value to set
* @func: Caller of this API
*
* Return: status of operation
*/
QDF_STATUS ucfg_nan_set_ndi_state(struct wlan_objmgr_vdev *vdev,
uint32_t state);
QDF_STATUS __ucfg_nan_set_ndi_state(struct wlan_objmgr_vdev *vdev,
enum nan_datapath_state state,
const char *func);
/**
* ucfg_nan_psoc_open: Setup NAN priv object params on PSOC open