wlan: POSTASSOC link set after successful Reassociation

When a DUT is roaming, it should be ensured that
the POSTASSOC link should be set only after successful
reassociation with the new AP. This will take care of
the DUT not sending/receiving any data packets during
the Roaming process. For instance, there might be BT
co-existing with LFR and if the POSTASSOC link is set
without even completing a reassociation, then BT will
think that it is allowed to receive and send data and hence
starts data transfer.This might create a problem for the
DUT in INFRA STA mode which is still in the process of
reassociating. The AP may Deauth the STA thinking that the
STA is trying to send data packets even before completing
the reassociation.

Change-Id: I1d19c243b494a58ce6eb64e23337cf72ab24e443
CRs-Fixed: 525861
wlan: Add ini param to control antenna diversity

Add gAntennaDiversity parameter in ini file with
values mapping to the following behavior:
0 = disabled
1 = Ant 1
2 = Ant 2
3 = Adaptive

CRs-Fixed: 518527
Change-Id: I27e8a02cb4a8e2e3cbd2ae37c12cb8523103cbce
wlan: Updating dwelltime in run time.

Implemented IOCTLs to get and set DWELL time.

Change-Id: Ia64f19e9d1dc0211ded4a84f6b80ebe24c819d27
CRs-Fixed: 507132.
wlan: Make FW rssi monitoring config independent of roaming

Presently, FW Rssi monitoring is disabled by default and only when
any type of roaming is enabled (11r,CCX,LFR) RSSI monitoring is
enabled implicitly and sent down as a part of ENTER_BMPS_REQ.

This does not satisfy the requirement, when SETROAMMODE is re-enabled and
RSSI of the AP is getting worse, DUT should roam; because disabling
SETROAMMODE results in disconnection (as expected) and if the DUT
immediately connects to new AP and ENTER_BMPS_REQ is sent down
with FW RSSI Monitoring disabled. Now if the SETROAMMODE is enabled
runtime, OFFLOAD_SCAN (REASON_CONNECT) is sent to FW and thresholds
are registered, but FW RSSI Monitoring is still disabled, hence next
roam does not happen.

The fix for this issue is to make FW RSSI Monitoring independent of
roaming. Enable FW Rssi monitoring by default and this value
goes to FW as a part of initial config value exchange and now
RSSI monitoring is aligned with NTBTT, there are no extra wakeups
caused by this. This value can remain always ON irrespective
of enabling/disabling Roaming.

Config parameters (Rssi filter period, FW RSSI Monitoring
and Number of beacons per RSSI average) values sent down to FW during
initial exchange (driver load) is same as ENTER_BMPS_REQ.
Sending these values again in ENTER_BMPS_REQ is not required
(can be removed). This is kept as-is for now to support
backward compatibility with the older host running on new FW.

As a part of this change, LFR (FastRoamEnabled) dependency on
FastTransitionEnabled config is completely removed.

Change-Id: Ib40916670e84a1986794f561f42a910d5ed1b6fd
CRs-Fixed: 505327
wlan:Delete STA entry from LIM hash table

In DEL STA failure scenario, WDI and HDD layer deletes
the STA entry from their respective tables but it is not
deleted from LIM hash table.So,to avoid this removing the
STA entry from LIM hash table as well.

Change-Id: Ibe3f2f50e40727072882c600d112f31fa4512bd6
CRs-Fixed: 512043
Wlan: Revison 3.2.3.161

Revision 3.2.3.161