Vignesh Viswanathan edc7ba6297 qcacld-3.0: Handle each frame in Roam Frame Event independently ... Currently the wmi_roam_synch_frame_event_id is sent from the FW before the roam_synch event if the size of the beacon/probe, reassoc request and reassoc response frames exceeds the max WMA message size. In such scenarios, the FW sends two wmi_roam_synch_frame_event_id events with the first event containing beacon/probe and reassoc response frames and the second event with reassoc request frame. However, driver is dropping the first event with beacon/probe and reassoc response frame as the reassoc request is not present in that event. This is expected in the first frame and the driver should handle each frame independenly in the wma_roam_synch_frame_event_handler. Remove the check for beacon/probe and reassoc request frame while handling reassoc response frame in wma_roam_synch_frame_event_handler. Change-Id: Ic66dd7f93da0de32715cf36be520128d2a1efc8e CRs-Fixed: 2325217		2018-10-06 00:01:22 -07:00
..
inc	qcacld-3.0: Rate limit mgmt frame error messages	2018-10-03 18:37:22 -07:00
src	qcacld-3.0: Handle each frame in Roam Frame Event independently	2018-10-06 00:01:22 -07:00