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: Ied864c85ff8143d44f0eb35e0f49166f88e578ba
CRs-Fixed: 2100172
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: Ib8b11a064c448c1f1995bf192c6a70f49391cbd5
CRs-Fixed: 2100194
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: I78b16ac511713e20c5b4a7d53315149a80d72e13
CRs-Fixed: 2100192
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: Ic173dab22fa7279634e913a28530a5b405b0a775
CRs-Fixed: 2100166
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: I58246d49ae36d6555b21832d12c2ca6735c5a507
CRs-Fixed: 2100143
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: I8a8189717acf389b326325c1edb64b7df904fa47
CRs-Fixed: 2100141
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: I8404fa2fc32269a92522f6ae15f8d9d1a8aebf85
CRs-Fixed: 2100140
pe_roam_synch_callback creates new pe session and initializes
the varible bssIdx with add_bss_params->bssIdx which is not
initialized. When beacon miss event happens, it can't disconnect
with the AP because the session is not found for bssidx zero.
Change-Id: I44b79fe7ee0a8fc4ecc6f41e2574c203b0755827
CRs-Fixed: 2094326
qcacld-2.0 to qcacld-3.0 propagation
While processing SETROAMMODE IOCTL, invalid argument is passed to
kstrtou8() due to which error is returned for valid command.
To fix this, invoke kstrtou8 with base 10.
Change-Id: I78b10b6c13338c3afa420792e2ddbc7c945a7fec
CRs-Fixed: 2101398
Tx descriptors' state info, such as vdev pointer, vdev ID and
ref_cnt, are protected by a spin lock during freeing, but not
protected by the same lock during allocation. Correct the
discrepancies to avoid a NULL pointer dereference issue
Change-Id: Ie0fb634a893a8d33888f7f1f6685a4fb7219e308
CRs-Fixed: 2091379
Adds the following support:
1) Add FILS IE's to assoc request.
2) AEAD encrypt/decrypt the assoc request/response frames for FILS
3) Process/Verify the Assoc response for the FILS params
4) Plumb the Auth keys to firmware after successful FILS assoc
5) Update the user space with Auth key details
Change-Id: I57f6319cecdf10e08047b510321b885c3cd711b5
CRs-Fixed: 2030038
qcacld-2.0 to qcacld-3.0 propagation
In the current code, there is no log of rssi value in wlan_hdd_get_rssi.
To fix this, add print for rssi.
Change-Id: I7db04c7defd26d2cd9792e96805ff524d88bb9b4
CRs-Fixed: 2045201
During the driver unload driver de-registers the netdevices taking
hdd_init_deinit_lock and if any userspace entity trying issues the
interface taking the rtnl_lock resulting in the deadlock as one
thread is waiting for the rtnl_lock to be released taking the
hdd_init_deinit_lock and other thread is waiting for hdd_init_deinit_lock
taking the rtnl_lock. Since the driver is unloading reject the
interface up request before acquiring the hdd_init_deinit_lock.
To address this issue do not proceed with hdd_open if unload is in
progress.
CRs-Fixed: 2078720
Change-Id: Ie8c8bba8d142312d3504c40a839343e16fc3b31e
kmsg is flooded with excessive logs from lim_enable_11a_protection.
Fix is to change log level to debug.
Change-Id: I05d8def15660cc519c44870359ff6c337a44ed60
CRs-Fixed: 2072944
Linux kernel 4.12 renamed center_freq_seg2idx to center_freq_seg1idx and
center_freq_seg1idx to center_freq_seg0idx. Add conditional compilation
to access the correct fields based on the kernel version.
Change-Id: Id8c20f9e47eecdbdf121c88cb5e017f662e2e15e
CRs-Fixed: 2091058
The header guard within csr_inside_api.h ends before the end of the
file. Move the end of the header guard to the end of the file.
Change-Id: I7c9e62b9eaee8815f6d1e496d88b6b79f489299b
CRs-Fixed: 2090171
Currently, host driver sets bitmap of allowed action frames to fw.
For a particular action category, there are certain action id
frames which are not processed. This causes host wakeup and leads
to power drain.
Set action id along with action category to fw for action frames
to be allowed to host driver.
Change-Id: Ifa0b40b290fcabb9ce5e48f69bd462aebb9017ac
CRs-Fixed: 2072123
net_device->last_rx has long since been depreciated, and was finally
removed in Linux kernel 4.11. Simply remove any reference to the field.
Change-Id: Ia7896707f8ebc7105fcc4b89dd9d1e7f9334d584
CRs-Fixed: 2093262
In the case of low memory allocation failures, the system should be able to
continue functioning after the connect_service failure.
Change-Id: Icd054d541aa95dbf4099426cf73f3dfe6c2c4565
CRs-Fixed: 2097391
Linux kernel versions 4.12+ define WLAN_AKM_SUITE_FT_8021X. Avoid
redefining WLAN_AKM_SUITE_FT_8021X when compiling against 4.12+ Linux
kernels.
Change-Id: Iaaaeb0c348933c69034cb852191bed4d6a6862b1
CRs-Fixed: 2093922
Add changes to add support of sending and parsing
authentication packets based on 80211ai specifications.
Change-Id: I684dbc89945ba3aef3186c872e5e1f7564d7e44c
CRs-Fixed: 2028113
Add support for PMK and PMKID cache based on either bssid or
ssid + cache identifier.
Change-Id: I23c50472e4c2032b953ccf264fc4cadb2ea573ca
CRs-Fixed: 2028113
Add changes to parse fils indication element and add the info
to bss descriptor for further use.
Change-Id: If4b56435180a226438c9f0afdda0f58a26854d88
CRs-Fixed: 2028113
The Linux Coding Style eschews the encoding of type information into
names, so rename struct hdd_wext_state_s to align with that guidance.
Change-Id: I27fffbb103aab157356c98d8af2a8716512ef417
CRs-Fixed: 2094519
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 qcmbr_data_t & qcmbr_queue_t
typedefs do not meet any of those criteria, so replace them with well
named structs.
Change-Id: I8faca21ec5e9fa6d1b46fa4cb77764ca7de2e6b9
CRs-Fixed: 2097978
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_priv_data_t typedef does
not meet any of those criteria, so replace it with a well named
struct.
Change-Id: I1f31b7d8035e7025abd23cede7b2e8830a8db5d2
CRs-Fixed: 2094518
Auto ps timer is started as part of the interface up
but not disabled as part of the interface down.
Meanwhile if interface down happen hence sme session
get deleted. But if ps timer expire later then it try
to access invalid sme session and lead to abort.
As a part of fix, Disable auto ps timer on interface down.
Change-Id: If67f7ec66d7dea7b8e7e674dc86efe7124244dde
CRs-Fixed: 2061845
Napier does not yet support PCIe link-down suspend. For the time being,
prevent the PCIe link from going down during suspend by default on
Napier. This is to be reverted once Napier gets proper link-down
support.
Change-Id: I55adea9a1421977fc018193ecfa25eeb51987192
CRs-Fixed: 2092853
