The Linux Coding Style enumerates a few special cases where typedefs
are useful, but stresses "NEVER EVER use a typedef unless you can
clearly match one of those rules." The hdd_context_t typedef does not
meet any of those criteria, so replace references to it with a
reference to the underlying struct.
Change-Id: Ib6fe81f9537bd760447b3e0f5fedee44499c302c
CRs-Fixed: 2100213
The Linux Coding Style enumerates a few special cases where typedefs
are useful, but stresses "NEVER EVER use a typedef unless you can
clearly match one of those rules." The hdd_context_t typedef does not
meet any of those criteria, so replace references to it with a
reference to the underlying struct.
Change-Id: I996f41049c1be0e37f27a8c9a032d69f5c58a390
CRs-Fixed: 2100208
The Linux Coding Style enumerates a few special cases where typedefs
are useful, but stresses "NEVER EVER use a typedef unless you can
clearly match one of those rules." The hdd_context_t typedef does not
meet any of those criteria, so replace references to it with a
reference to the underlying struct.
Change-Id: I4d204f1fc4ef0c8d2d2664544ca470d1f31099aa
CRs-Fixed: 2100159
The Linux Coding Style enumerates a few special cases where typedefs
are useful, but stresses "NEVER EVER use a typedef unless you can
clearly match one of those rules." The hdd_context_t typedef does not
meet any of those criteria, so replace references to it with a
reference to the underlying struct.
Change-Id: Ie0a9961cfe67a7549469756ec0df08546aa94cc0
CRs-Fixed: 2100163
The Linux Coding Style enumerates a few special cases where typedefs
are useful, but stresses "NEVER EVER use a typedef unless you can
clearly match one of those rules." The hdd_context_t typedef does not
meet any of those criteria, so replace references to it with a
reference to the underlying struct.
Change-Id: Iea06364201509e916b3e9c60a2248eaf29402720
CRs-Fixed: 2100212
Currently 802.11p channels are by default enabled.
To make it configurable, use ini value gDot11PMode.
Change-Id: I70417f79d179649df9597c02ec51fe46ef953b91
CRs-Fixed: 2098677
wma_delete_bss is stuck for more than
400ms in failure scenario due to pending
tx packets to drain.
-Decrease the wait time to 20ms(2ms*max_wait_iterations)
to avoid the delete bss stuck issue.
-Tx drain wait feature added for LFR2.0
feature so moved the code under the LFR2.0
macro.
Change-Id: I33b56bb627ac914ca6fe96949de373b015853fc9
CRs-Fixed: 2097269
Add a separate variable to store the band value. Since the
value can be set at run-time, config data structure cannot be
used to store the runtime value. Also apply the configuration
restrictions while calculating this band value.
Change-Id: Id6df155b7ecfbe9ca84e489b2dd099cdd0cbcc8f
CRs-Fixed: 2085746
Some of the callbacks in mac context gets initialized to NULL when SSR
is triggered and up on reinitialization of driver, those callbacks need
to be re-registered.
CRs-Fixed: 2078706
Change-Id: I0ce9b0ab2680e7403536d6b4dd745c2bcb10791a
For STA-DUT, when host receives the beacon forwarded by firmware which
contains NSS update, host discards that beacon if channel bonding is
disabled from INI. This is incorrect behavior.
When channel bonding is disabled from INI and host should discard the
beacon when it contains channel width related updates.
Change-Id: I76b42caec6ed0faea7b1650407ff5c1565ac6947
CRs-Fixed: 2059895
In Dual band SAP+SAP, if channel change for a SAP, the SAP get
stuck in eSAP_DISCONNECTING state, waiting for channel change
indication for the concurrent SAP, which may never come as this
is Dual band SAP+SAP and both are on different bands.
Now when stop adapter is called for this SAP, the stop BSS fails
as its already in disconnecting state and due to this it is not
deleted cleanly.
To fix this if DBS is enabled change the channel of the AP on
which CSA was initiated without waiting for other SAP interface.
Change-Id: I54d903d4fc0694b16c1f1debf52ffe2a6dad0ba9
CRs-Fixed: 2097002
For each WLAN_SVC_LTE_COEX_IND event, SCM
will stop/start hostapd. In middle of
Stop/restart hostapd, the current unsafe
operation channel is not changed. If multiple
FW LTE coex event are uploaded during this
time, the WLAN_SVC_LTE_COEX_IND could be
delivered multiple times. And then the hostapd
will stop/start several times.
Fix by skipping unsafe channel checking
and SAP restart when the unsafe channel list
has no change.
Change-Id: I756f317ba39f97c673fa54b382191a6429435b1e
CRs-Fixed: 2078725
__wlan_hdd_cfg80211_set_mac_acl() contains a local variable
p_cds_context that is written but never read, hence it is unused.
Therfore remove the variable.
Change-Id: I99051fbfb5e44791514a5086eb9cf33f773ffbee
CRs-Fixed: 2102503
Use lockless sme API to get valid channel list from sme instead of
sme_get_cfg_valid_channels to avoid deadlock.
Change-Id: I481824cb116244b9c13665d6a0ee88e28c88cf66
CRs-Fixed: 2063060
Handle the scenario where no common channel between PCL & the
favorite channel list is found.
Change-Id: I560d7ef861d89f3f4a0c63afacd0ffbf6aaa976e
CRs-Fixed: 2063060
If SAP is up & STA is coming up next(or vice versa) on a different
channel causing MCC, move SAP to cause SCC or DBS. This logic is
enabled only if gWlanMccToSccSwitchMode is set to
QDF_MCC_TO_SCC_SWITCH_FORCE_WITHOUT_DISCONNECTION or
QDF_MCC_TO_SCC_SWITCH_WITH_FAVORITE_CHANNEL.
Change-Id: I16615d828a285762133ee3533339320ef119b3d3
CRs-Fixed: 2063060
If STA is up & SAP is comings up on a ACS derived channel causing MCC,
move SAP to the other band if DBS is supported. This logic is enabled
only if gWlanMccToSccSwitchMode is set to
QDF_MCC_TO_SCC_SWITCH_FORCE_WITHOUT_DISCONNECTION.
Change-Id: I48d809f83921292f51ca1735bff4c4d6dd339975
CRs-Fixed: 2063060
If STA is up on a a DFS or passive or LTE unsafe channel & SAP is
comings up that causes MCC, move SAP to the other band if DBS
is supported. This logic is enabled only if gWlanMccToSccSwitchMode
is set to QDF_MCC_TO_SCC_SWITCH_FORCE_WITHOUT_DISCONNECTION.
Change-Id: I5d393a21301f3fa838f7cf38620fb1d57ae1d57a
CRs-Fixed: 2063060
If SAP is up & STA comes up or moves to a DFS or passive or LTE
unsafe channel that causes MCC, move SAP to the other band if DBS
is supported. This logic is enabled only if gWlanMccToSccSwitchMode
is non zero.
Change-Id: I56f78dfaedec31c4c41aea6ac8c66261c9ad4c91
CRs-Fixed: 2063060
The cdp_peer_ops register_ocb_peer() method currently takes a cds_ctx
parameter. Converged datapath APIs should not require the MCL-specific
CDS context, and in fact it is not required by the MCL implementation,
so remove it from all OCB peer registration APIs.
Change-Id: I873eeb472f463ac76f30de5a9013783565be916d
CRs-Fixed: 2103451
Currently wma_register_roaming_callbacks() has a cds_ctx parameter. At
one time this was necessary since the global context was required to
get the module-specific context. However the global context is no
longer required for this purpose, so remove the unused parameter.
Change-Id: Ida681fb20dd98a46f385f1e04662f72a334c68bf
CRs-Fixed: 2103626
Log the IP header source and destination address for the first Rx
packet received after host wakeup.
Change-Id: Ie8cf71c8ce913378687ad2c79ab9d5f46c0c2419
CRs-Fixed: 2010971
Currently tCsrRoamStruct contains a g_cds_context field to hold a
pointer to the global context. This pointer is never actually used, so
remove it. In addition remove an unnecessary retrieval of the global
context pointer from csr_packetdump_timer_stop().
Change-Id: Id8137d6e9eef87f90c01f803982a6ffdc44fbe20
CRs-Fixed: 2102464
Currently wma_get_wcnss_software_version() takes a p_cds_gctx
parameter which it does not use, so remove it.
Change-Id: I86a5893a9407bad034a32c105aec92d4e6054744
CRs-Fixed: 2102549
The Linux Coding Style enumerates a few special cases where typedefs
are useful, but stresses "NEVER EVER use a typedef unless you can
clearly match one of those rules." The hdd_context_t typedef does not
meet any of those criteria, so replace references to it with a
reference to the underlying struct.
Change-Id: I80d863c19d4a7330a87c6ea74fbfcefee56cca2c
CRs-Fixed: 2100206
The Linux Coding Style enumerates a few special cases where typedefs
are useful, but stresses "NEVER EVER use a typedef unless you can
clearly match one of those rules." The hdd_context_t typedef does not
meet any of those criteria, so replace references to it with a
reference to the underlying struct.
Change-Id: Ie7fd294d48ba17a29b28fb9b8cbc5865f467f8ba
CRs-Fixed: 2100203
The Linux Coding Style enumerates a few special cases where typedefs
are useful, but stresses "NEVER EVER use a typedef unless you can
clearly match one of those rules." The hdd_context_t typedef does not
meet any of those criteria, so replace references to it with a
reference to the underlying struct.
Change-Id: I1eceef88a686678814b4463ad924f9dfb1a06b29
CRs-Fixed: 2100201
The Linux Coding Style enumerates a few special cases where typedefs
are useful, but stresses "NEVER EVER use a typedef unless you can
clearly match one of those rules." The hdd_context_t typedef does not
meet any of those criteria, so replace references to it with a
reference to the underlying struct.
Change-Id: Ie13624b984a39da923511c1c75a5b51ab29eca18
CRs-Fixed: 2100197
The Linux Coding Style enumerates a few special cases where typedefs
are useful, but stresses "NEVER EVER use a typedef unless you can
clearly match one of those rules." The hdd_context_t typedef does not
meet any of those criteria, so replace references to it with a
reference to the underlying struct.
Change-Id: I50d6e07d5d765f9cc769e880621740db3df5ab09
CRs-Fixed: 2100187
