The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier channelEnabledState to be compliant.
Change-Id: I26a676e216b2a8c5964f3e903cbda884769db284
CRs-Fixed: 2418191
The Linux Coding Style frowns upon mixed-case names and so-called
Hungarian notation, so rename HDD identifier fValidChannel to be
compliant.
Change-Id: Ic591e0e194b3444499518f7fd3c273adb6189423
CRs-Fixed: 2418190
The Linux Coding Style frowns upon mixed-case names and so-called
Hungarian notation, so rename HDD identifier fEnableSNRMonitoring to
be compliant.
Change-Id: Ic613f39d0d267ba7e8cb72cd0cc3bf261a029278
CRs-Fixed: 2418189
Currently in case of SAP, supported mode of station received
in assoc request is not getting cached.
Add support to cache the supported mode of station received
in assoc request request in sta_info.
Change-Id: I9820ae2d65fc529a1ab16424f6732fd273da3ae0
CRs-fixed: 2419957
hdd_init_deinit_lock has been obsoleted by the addition and integration
of the Driver Synchronization feature. Remove hdd_init_deinit_lock.
Change-Id: Ia1b9e4279f42023ba2c956224ceabd02d8b4c6d4
CRs-Fixed: 2420766
Upon client connection to SAP, WLAN IPA will pass a message
containing client MAC address and ethernet header offset to
IPA driver. Per WDI 3.0, there's no frag_header and
ipa_header prepended in front of ethernet header. Thus
ethernet header length is passed to IPA driver as header
length during interface registration. But in per-client
message, offset passed to IPA driver still accounts for
length of frag_header and ipa_header. As a result packet
queued to event ring will have wrong ethernet header.
And this causes IPA to WLAN TX HW path not work as expected.
Fix is to define frag_header and ipa_header as 0 sized
structure for WDI 3.0 so that ethernet header offset will
be 0.
Change-Id: I58cdf78732ad2909bf89058f2a5bc24c42f841d2
CRs-Fixed: 2421315
The bus bandwidth compute is a periodic activity that calculates the
required DDR bandwidth needed by the wlan driver. Currently it is
implemented using a spinlock, a flag, a timer, and a kernel work.
qdf_periodic_work effectively implements the same behavior, so use it
instead.
Change-Id: I1c71a1eb430317d2ac167b7c1ba94fb190deef4a
CRs-Fixed: 2410047
Propagation from qcacld-2.0 to qcacld-3.0
If AP sends unsolicited neighbor reports to station proactively,
the cached neighbor report list will grow longer and longer.
Fix it by purging the cache on reception of unsolicited neighbor report.
Change-Id: I2458607041caeb84cb553aa1b9fc6f4029a5cf1c
CRs-Fixed: 2419615
Per the Linux Kernel coding style, as enforced by the kernel
checkpatch script, pointers should not be explicitly compared to
NULL. Therefore within sap replace any such comparisons with logical
operations performed on the pointer itself.
Change-Id: I0f738f58e64fdf20957d57775c3570fb4ccfc9f7
CRs-Fixed: 2418389
Currently there is no support to configure ito repeat
count when driver enters into wow mode.
Add support to configure ito repeat count with ini
gItoRepeatCount when driver enters into wow mode.
CRs-fixed: 2419137
Change-Id: I62d7e7df12342e9743c26e0147851347214a9ce7
Disable BMI for Lithium architecture instead of
CNSS2 as CNSS2 also used for Rome architecture.
CRs-Fixed: 2416745
Change-Id: I2d646eac483ca44689445faa1b3bbf7b0b3a05bb
If DBS 2x2 mode is supported, to operate in 2.4Ghz the driver needs to
be in DBS mode before vdev start/restart is sent on 2.4Ghz channel.
If STA is connected to a 5Ghz channel and the PEER AP switch from 5Ghz
to 2.4Ghz channel, it sends vdev restart without sending the HW mode
change to firmware.
Fix is to set HW mode before the initiating vdev restart if new channel
is 2.4Ghz and 2x2 DBS is supported and current HW mode is not DBS
Change-Id: I6dc57f37e155f0e29b17840e4e246de773f42b3e
CRs-Fixed: 2419642
As a step towards removing qdf_ssr_protect, register for the
replacement APIs, qdf_op_protect/unprotect.
Change-Id: Ica5802082b3be51f47bdf4ae0eb132b80c29b08a
CRs-Fixed: 2418432
In function __wlan_hdd_cfg80211_get_tdls_capabilities,
If tdls_support is true then user is notified wrong values.
Change-Id: Id177f94a841f7d6676de8b26664955194cdb0c16
CRs-Fixed: 2417950
In LIM there are two separate places where the code iterates over the
gpSession[] array and tests each &mac_ctx->lim.gpSession[i] for NULL.
These NULL checks are unnecessary, so remove them.
Change-Id: Ice7435b19cc9fc61ebe11537e0aa6acd1b61984d
CRs-Fixed: 2419289
Per the Linux Kernel coding style, as enforced by the kernel
checkpatch script, pointers should not be explicitly compared to
NULL. Therefore within ipa replace any such comparisons with logical
operations performed on the pointer itself.
Change-Id: I82e4bed12122ad5aea47650f6d75e72a52207883
CRs-Fixed: 2418401
Change Ib55b211e4fdab427aff8c04c8ac99e1af56c6edc ("qcacld-3.0: Rename
pMac in csr_api_scan.c ") previously renamed all instances of pMac in
csr_api_scan.c to align with the Linux coding style.
Subsequently change Iac183da52495aca07c6270edeb9f383ab49c1ff5
("qcacld-3.0: Add CFG items of power") reintroduced pMac in function
csr_save_tx_power_to_cfg(), so once again rename it in that function.
Change-Id: I5272cf71c422618ae0e3c042a99f7728192321f2
CRs-Fixed: 2420015
In QCA_NL80211_VENDOR_SUBCMD_SET_TRACE_LEVEL command handler
when nested attributes are getting parsed no NLA policy is
used, as no NLA policy is defined for MODULE_ID and TRACE_MASK,
these attributes will be treated as NLA_UNSPEC types and can
have a length of zero bytes. Later when these attributes
are accessed using nla_get_u32() this will result in OOB
read.
Change-Id: I7d4913feccb00877ac5f40bab8ff5e9e3891756f
CRs-Fixed: 2410900
NON TX BSS may not respond to unicast probe request.
so dont send unicast probe request as part of association.
Change-Id: Ia36d71742e4632c6c979066a833bdc98b71bae9c
CRs-Fixed: 2415672
Mlme info is not updated for the new AP to which driver roamed and
also not updated for the old AP after driver roamed to new AP.
Also in some case when deauth is from peer the Mlme info is not reset
by driver for the disconnected AP.
As mlme info of the AP is not updated and it remain in associated state
The AGE out logic skip the AP and thus it never ageout.
Fix this by properly updating the MLME info of the AP during roaming
And disconnection.
Change-Id: Ib17499c8ab0c4725d146d7c09077c92661adbdd5
CRs-Fixed: 2419853
Currently, hdd_parse_vendor_acs_chan_config does not do null validation for
tb[SET_CHAN_CHAN_LIST] which can lead to null pointer derefrence.
Add null pointer check for tb[SET_CHAN_CHAN_LIST] in
hdd_parse_vendor_acs_chan_config.
Change-Id: I8914e38a5d98536a816c80d484dec9878753966a
CRs-Fixed: 2410809
The HDD driver operation inactivity timer has been rendered obsolete by
the addition and integration of the Driver Synchronization feature.
Remove the HDD driver operation inactivity timer.
Change-Id: I9c4f555f02edd9350cf44477c3ba6c84b61b09f7
CRs-Fixed: 2419307
Currently the driver just start the vdev according to the ini
params, without consdering the tx, rx chainmask supported by the
FW per band, per mac, which can lead to connection in 2x2, even
though FW is not capable of 2 antennas on a particular band.
Fix is to intersect both the tx, rx chainmask for both bands,
and change the ini to minimum of the nss supported by ini, and
the BDF setting of the chains.
Change-Id: Ib0e9bac19959bbcf9bade7dbd78674be4099a23d
CRs-Fixed: 2414103
Send MBSSID BSS information like profile number
and max profile count to firmware as part of VDEV
UP command.
Change-Id: I612f0be9c52fd61b25d1c884940f28ce9fe0872e
CRs-Fixed: 2399999
Monitor mode feature not required on SDXPRAIRIE, and disable
it to save memory.
Change-Id: I206ef4441cc64218cbdcea08aaa3ce584aa99bf0
CRs-Fixed: 2418590
The API's added in qal & qdf for abstracting the
OS calls are inlined and moved to the OS-specific
src directories.
Remove compilation of these specific files from qcacld Kbuild.
Change-Id: I0416ae721d4c86000672168da396966dd452363c
CRs-Fixed: 2418669
Per the Linux Kernel coding style, as enforced by the kernel
checkpatch script, pointers should not be explicitly compared to
NULL. Therefore within target_if replace any such comparisons with
logical operations performed on the pointer itself.
Change-Id: Id9b5185713b91b67ddf1d965a6c7e52508558d82
CRs-Fixed: 2418397
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier advertiseConcurrentOperation to be compliant.
Change-Id: I398a3a80caaafbb273a647b4c0b1f374db94d944
CRs-Fixed: 2418188
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier RSNMfpCapable to be compliant.
Change-Id: Ida5c11b7da71cd0f4b7a344ca5ddc1ab3975c840
CRs-Fixed: 2418185
In function tdls_delete_all_tdls_peers, bss peer can be NULL
if the bss peer is removed from vdev object. Hence, add NULL
check before getting its reference.
Change-Id: I9b2b03bc6db899c1c06de95ec5ee680d4b600aa7
CRs-Fixed: 2419567
Currently, whenever roaming is triggered after a successful roam scan
firmware sends a BTM query to current connected AP when it is 11v
capable. Driver completes roaming with candidates received as part of
BTM request from AP. STA respond to AP with BTM response after
successful initiation of roaming.
Now the requirement is FW could send "BTM query with a preferred
candidate list" after a successful roam scan for some roam scan reasons
like PER, LOW_RSSI, HIGH_RSSI, MAWC, DENSE etc. Preferred candidate list
is obtained as part of roam scan based on firmware bss scoring logic.
Add new ini "btm_query_bitmask" to configure the bitmask for roam scan
reasons which is sent to firmware as part of RSO start via wmi btm config
cmd. Fw sends "BTM query with preferred candidate list" only for those
roam scans which are enabled through this bitmask.
New INI: btm_query_bitmask
Min: 0
Max: 0xFFFFFFFF
Default: 0x8
Bitmask : 0x8 (LOW_RSSI) refer enum WMI_ROAM_TRIGGER_REASON_ID.
Change-Id: I24b538745f2ac88d4e5c990573234e0f8a881b1f
CRs-Fixed: 2408111
Per the Linux Kernel coding style, as enforced by the kernel
checkpatch script, pointers should not be explicitly compared to
NULL. Therefore within cmn_services replace any such comparisons with
logical operations performed on the pointer itself.
Change-Id: I7141cd900916bd4bbab1bc8c7a1b90589286582b
CRs-Fixed: 2418402
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier RSNMfpRequired to be compliant.
Change-Id: I9e4843c6ac8914580be5da668080802bdc0ec3c1
CRs-Fixed: 2418187
