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_adapter_t typedef does not
meet any of those criteria, so replace references to it with a
reference to the underlying struct.
Change-Id: I48952b52777b523d5b383ea4278b8390a4bc4a8e
CRs-Fixed: 2101054
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_adapter_t typedef does not
meet any of those criteria, so replace references to it with a
reference to the underlying struct.
Change-Id: I762cb4c29060d780dcf9647aebe7246610d8f923
CRs-Fixed: 2101057
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_adapter_t typedef does not
meet any of those criteria, so replace references to it with a
reference to the underlying struct.
Change-Id: I20d1395208566001aaa3c73689e1f9e6d2b5e94f
CRs-Fixed: 2101053
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_adapter_t typedef does not
meet any of those criteria, so replace references to it with a
reference to the underlying struct.
Change-Id: I07b27f87102c640124312b31b550cc394096019a
CRs-Fixed: 2101050
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_adapter_t typedef does not
meet any of those criteria, so replace references to it with a
reference to the underlying struct.
Change-Id: Iec3c0b0b2e59ac05ad352f5b4e6e2b4528a8b5be
CRs-Fixed: 2101051
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_adapter_t typedef does not
meet any of those criteria, so replace references to it with a
reference to the underlying struct.
Change-Id: I2e588aeaf26b85535afa86132aa4216ea630e958
CRs-Fixed: 2101049
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_adapter_t typedef does not
meet any of those criteria, so replace references to it with a
reference to the underlying struct.
Change-Id: Ic527031c7a2d0785ec179344cb3519bf65ea6a8c
CRs-Fixed: 2101047
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_adapter_t typedef does not
meet any of those criteria, so replace references to it with a
reference to the underlying struct.
Change-Id: Ib14b0e7bdd572294dc490043d5ae92ae2a4baa30
CRs-Fixed: 2101046
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_adapter_t typedef does not
meet any of those criteria, so replace references to it with a
reference to the underlying struct.
Change-Id: Id43c38784aadb07b5352d9ecc2c7dcb0e31dbcd8
CRs-Fixed: 2101045
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_adapter_t typedef does not
meet any of those criteria, so replace references to it with a
reference to the underlying struct.
Change-Id: I5be95445278bf120ddf8b1a01a6af8ddf7a0d5d7
CRs-Fixed: 2101039
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_adapter_t typedef does not
meet any of those criteria, so replace references to it with a
reference to the underlying struct.
Change-Id: I66ecfb6f5a478298c1300f7ac3086715aa66e4c2
CRs-Fixed: 2101044
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_station_ctx_t typedef does
not meet any of those criteria, so replace it with a well named
struct.
Change-Id: Idaa9c96dc757465d120b33c686d102ef29b31ca4
CRs-Fixed: 2101019
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_ap_ctx_t typedef does not
meet any of those criteria, so replace it with a well named struct.
Change-Id: I3084d902b405529f82ff9056f48a8c38392f50f5
CRs-Fixed: 2101017
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: Iadc364f1abf3159f7c258a01fd11628a86fcf820
CRs-Fixed: 2100215
Previously change "qcacld-3.0: Replace hdd_context_t in
wlan_hdd_hostapd.[ch]" replaced all instances of hdd_context_t in
wlan_hdd_hostapd.c. However a subsequent change introduced
__iw_get_peer_rssi() which has a new instance, so replace it.
Change-Id: I0a986b4e5255937732c41737ab65390e53257373
CRs-Fixed: 2103682
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
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 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
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
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
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: If9de2bcc171fc9746a45ab449ea23d330de67f22
CRs-Fixed: 2100179
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: I05332a554afe81f6b5f83a3541a312bfbdc2ace9
CRs-Fixed: 2100177
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: Ia65c6c8cab90c254fd12c7ada834ebdd6ffeeb47
CRs-Fixed: 2100176
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: Ia6cbe718dec3dc1c3b8bae19a84408d439b21717
CRs-Fixed: 2100174
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: I84f5cc357c960d070eda7155bee7a6fe2373aa95
CRs-Fixed: 2100171
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: Iccab34c5bf91b23af6a5b4f97386b8bed949fc79
CRs-Fixed: 2100168
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: I1d0c53f3b83a15e3d4c4766edd832ed4450e5a15
CRs-Fixed: 2100162
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: I3d3d82e1c5c7b70d6afab98f2c81b5d317ade628
CRs-Fixed: 2100160
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: I995c57774d472336294e4190708755742eb49e3f
CRs-Fixed: 2100157
