Abhinav Kumar b96b746a50 qcacld-3.0: Don't enable WOW_BEACON_EVENT by default for STA ... While processing QCA_WLAN_VENDOR_BEACON_REPORTING_OP_START vendor cmd, the expectation is FW should not wakeup host if host is in wow mode. Wakeup of HOST happens purely based on Nth beacon WMI event WMI_VDEV_PARAM_NTH_BEACON_TO_HOST config to firmware where host gives Nth value and MSB bit to indicate whether to wake up host or not. MSB bit is 1 means fw should not wakeup host(By default MSB bit is 0). WOW_BEACON_EVENT registration on host is required only in case if HOST sends WMI_RMV_BCN_FILTER_CMDID in order to allow fw to send connected AP beacons. Currently, HOST sends NTH BEACON CMD to fw with MSB bit of Nth value equal to 1 in order to allow send connected AP beacons to HOST only if HOST is not in wow mode. Fix is to remove default WOW_BEACON_EVENT registration for STA on host. Change-Id: I4717925fbcb38efb14f3336706f93d90f7a3888e CRs-Fixed: 2496594		2019-08-01 16:24:04 -07:00
..
core	qcacld-3.0: Don't enable WOW_BEACON_EVENT by default for STA	2019-08-01 16:24:04 -07:00
dispatcher	qcacld-3.0: Rectify max value of gEnableDynamicDTIM	2019-07-19 07:31:04 -07:00