wlan: Move staInfo to sapContext

Currently staInfo is maintained in pAdapter.As a
part of HT40 2.4Ghz SAP feature,40Mhz intolerent bit
needs to be checked for every STA that gets connected
to SAP.This bit is checked in SAP module but the
staInfo is present in pAdapter and pAdapter is not
accessible in SAP module.
So staInfo cannot be accessed in SAP module.

Changes are done to move the staInfo in sapContext.

CRs-Fixed: 752276
Change-Id: I07bdaf7ef40b405edd900467a7618e1fdd75d995
prima: Update the capabilities from most recent beacon/probe rsp

Few peer (GO) devices are toggling the capability bits in the
beacon and probe response frames more frequently. At present the
host will get the capabilities from scan results. But After scan
if the peer device changes the capabilities then host is not
updating its capabilities. This is leading to disconnection.

Change-Id: Iae159c95d994c04158271d8a33dd75ca054c2157
CRs-Fixed: 759388
wlan: During SSR ensure that driver threads complete their work

TX, RX and MC Threads should complete exexution before
the exit routine tries to free the dynamic data these threads
are trying to process. The current implementation does an
interruptible wait for completion of the threads; but it has been
observed that if the process which initiated the driver unload
receives SIGKILL while waiting for threads to complete, the process
will continue without waiting for threads to complete and the threads
will try to access invalidated data after the module has been removed
leading to a kernel panic. To fix this make the wait uninterruptible
during SSR and ensure that the driver threads complete execution
before the driver exits.

Change-Id: I77088bf15787dfdfb213d3f0fcc8348190d0df95
CRs-Fixed: 752958
Wlan: Release 3.2.3.457

Release 3.2.3.457

Change-Id: I6c916c8a56892573e3b5d3096d6a71c5b284bf13
CRs-Fixed: 688141