Currently the switch -DCHANNEL_HOPPING_ALL_BANDS is inferred by
examining a seemingly unrelated configuration option. In order to
clearly separate setting the configuration from applying the
configuration create a new CONFIG_CHANNEL_HOPPING_ALL_BANDS
configuration parameter.
Change-Id: Icc9aef38445cdcd9269210b578b1e1be2fe18ac9
CRs-Fixed: 2224811
Currently the switch -DWLAN_LOGGING_SOCK_SVC_ENABLE is inferred by
examining a seemingly unrelated configuration option. In order to
clearly separate setting the configuration from applying the
configuration create a new CONFIG_WLAN_LOGGING_SOCK_SVC configuration
parameter.
Change-Id: Ic542512e3440453ef9f320297cf18f73f92fb2e3
CRs-Fixed: 2224810
Define a separate configuration option for legacy WiFi positioning and
use that option to set the associated ccflags macro.
Change-Id: I43cc04b3730687bf6298c66af7c42a9d6d9db80c
CRs-Fixed: 2224809
Define separate configuration options for the various Lithium
features and use those options to set the associated ccflags macros.
Change-Id: I08fee39c76963b102611b134346fe5edc95a0835
CRs-Fixed: 2224808
Define separate configuration options for the various Helium
features and use those options to set the associated ccflags macros.
Change-Id: Ia221aa3690ecbe37ac6568fa54876c77e338e2f6
CRs-Fixed: 2224807
Define separate configuration options for the various Adrastea
features and use those options to set the associated ccflags macros.
Change-Id: Ie418140dd21038ee3fd6eb3ecfd5d031bf1432ed
CRs-Fixed: 2224806
Add new ini item "ho_delay_for_rx" to set delay Hand-off
period. For LFR 3.0 roaming scenario, once roam candidate
is found, firmware waits for minimum this much duration
to receive pending rx frames from current BSS before
switching to new channel for handoff to new AP.
Change-Id: Ided9a81e9402259f5df6b42926b3fa336b6bb4d0
CRs-Fixed: 2221748
WMI cmds should be blocked, before calling HTC stop
to avoid the race condition in the system
Change-Id: I677c55cd96ea6af973595eec1e759641fbea109a
CRs-Fixed: 2193653
Define a separate configuration option for legacy TX flow control and
use that option to set the associated ccflags macro.
Change-Id: Id14ac79280d3bf809c1e85bde4d5c7037a3ea766
CRs-Fixed: 2224629
ACS in 5G channels for STA connected in 5G non DFS channel can result
SAP starting on DFS channel. Making MCC on DFS channel. This is
leading to FW panic if STA tries to roam during SAP is
detecting radar.
Avoid SAP starting on DFS channel if STA connected on 5G non DFS
Remove DFS channels from scan list before acs, if MCC is disllowed.
So, that DFS channel is not selectecd after acs.
Change-Id: I717309b81934852bfd93146b233db6f7fb03f252
CRs-Fixed: 2215332
Race condition in STA connection and Channel switch of
Softap can result in MCC for STA+SAP scenario. Even
though Force SCC is enabled.
As part of STA connection in association handler SAP
restart is checked. If Channel Switch for SAP interface
is in progress at the same time. Then depending on SAP
Channel MCC can be resulted.
Check for SAP restart in the function hdd_hostapd_sap_event_cb.
Change-Id: Ic4ba8790d604f184eb8030e4fe06c5e76f9a62bd
CRs-Fixed: 2205482
Currently, Logic to reject concurrent ACS scan is present
in Hdd context and variables for this context is common for
both softaps(softap1 and softap2). Due to this in case of dual
band SAP mode, if an ACS scan is in progress for softap1 then
driver rejects any ACS scan on softap2, which is not acceptable.
Fix is to move logic to reject concurrent ACS scan from
hdd context to adapter context.
Change-Id: I9d2b437523ef6ac5794e7952ac6cd35d1c2f778b
CRs-Fixed: 2206499
Whenever hw_mode=any is set in hostapd.conf, BAND_ALL is sent to
HOST driver from hostapd. ICM module doesn't support BAND_ALL
and so HOST driver internally changes the band to BAND_2G or BAND_5G
based on acs_freq_band and update the channel list and ch_width
accordingly.
ICM module supports BAND_ALL now so don't do any optimization on
band in HOST driver.
Change-Id: Ia0b554f72ba0d5063ff622edbe1fa7113b984142
CRs-Fixed: 2224675
Currently there are many cases where ccflags-y is set by logic:
ifeq ($(CONFIG_FOO), y)
ccflags-y += -DENABLE_FOO
endif
In order to align with Linux style reduce such simple cases to:
ccflags-$(CONFIG_FOO) += -DENABLE_FOO
Change-Id: Ibe700701d25c3a2944fa2f2eabf528b04b59bbdd
CRs-Fixed: 2223862
In order to more closely comply with Linux look and feel replace the
temporary variable CDEFINES with direct use of ccflags-y.
Change-Id: I801e61644f583ea213c9d699b318d328ae4ba1c2
CRs-Fixed: 2223861
In preparation for fully file-driven configuration create config
items for (almost) all -D switches which are currently being set
unconditionally.
Change-Id: I067b13e11c9cdf3a0355c2e64ab3770088118afa
CRs-Fixed: 2223860
Add WLM setting to "csr_get_config_param"
to avoid the setting lost when set back by
csr_change_default_config_param.
Change-Id: I539a4a87f55365c701a7149784e92c60fb6c5383
CRs-Fixed: 2223340
The change for the CR 2211133 caused compilation issue in LE
branches. This reverts commit with
change Id-I45943ae76d8fcf7b53e1f064c462d01cd6d00dcf
Change-Id: I069f1a4ae8ad320f5a073ee072dd772e05c5fc5d
CRs-Fixed: 2222536
Currently, sta's adapter.rssi does not reset when disconnect
with the previous ap and for new connection there might be no
valid rssi so it will get 0 when hdd_get_station_statistics_cb
or hdd_get_rssi_cb is invoking. Then it uses the previous ap's
rssi for the new conneciton.
Per the code logic, it is ok to set adapter.rssi with 0 value.
Because it invokes hdd_get_rssi_snr_by_bssid to get the
rssi & snr when issue happens.
Change-Id: I737cfcf16d58501546f2fceab06ed1e5418e7b06
CRs-Fixed: 2199782
Since WLAN host driver is regulatory offload design,
regulatory notifier from CORE should always be ignored.
Change-Id: Iaf23bdd1606e84cb309101246088ce6d506aa78b
CRs-Fixed: 2215884
The driver contains considerable debris from the obsolete WOWL
messaging, so clean it up.
Change-Id: I432f7fc1567b0aa31a7be758c05f2213340baed0
CRs-Fixed: 2223859
Currently -DWLAN_FEATURE_GTK_OFFLOAD is being set twice, once
unconditionally and once based upon CONFIG_GTK_OFFLOAD. Since this is
properly featurized, remove the unconditional setting so that the
setting is correctly controlled by the configuration.
Change-Id: I6f820990dc48304f18f78ec59005c2188a677094
CRs-Fixed: 2223858
Currently -DWLAN_ENABLE_AGEIE_ON_SCAN_RESULTS is unconditionally added
to all builds. Since this feature may not be required for all targets,
create a CONFIG_AGEIE_ON_SCAN_RESULTS feature flag to enable this
feature.
Change-Id: Id5a82a85f4484ca710d4b309355fe3ee0d05883e
CRs-Fixed: 2223857
Currently Kbuild sets a HAVE_CFG80211 flag based upon whether or not
CONFIG_CFG80211 is configured. The presence of this flag implies that
cfg80211 is optional. However in reality this is a required module, so
remove the confusing flag and instead make the underlying code always
present.
Change-Id: Ia039968cad6f311091e09d4b82805c7bbc5b83f8
CRs-Fixed: 2223856
WMI non_tlv is not used for MCL targets and hence compile
out WMI non_tlv object file from Kbuild.
Change-Id: I0ee9376065dffb0f959ef8ba47435cc38a3d7d55
CRs-Fixed: 2216856
