Based on new requirement, add aliasing for gNeighborLookupThreshold
ini and update the range of this ini as well.
Change-Id: I0a62e209d6a62001d6aec48849c4900062ae5bc7
CRs-Fixed: 3011060
Adding flags to support FR of Modularization of
monitor mode for Hastings to avoid compile issue.
Change-Id: I7be63661dde17179c8eb5fb5e5fd9b2dc0c9f4af
CRs-Fixed: 3011407
Incase of non-6ghz, the peer width is
updated while extracting HT and VHT
capability. For 6Ghz, the HT and VHT
capabilities may not be present and
because of which the peer channel width
gets updated as zero (20 Mhz).
To fix this, fill the channel width for
peer if session is 6ghz and peer supports
HE Capabilities.
Change-Id: Ie4d8f3a3a364af2c47e6b3d7309ee1287652ae06
CRs-Fixed: 3010063
In hdd_set_primary_interface:
1. When dual sta doesn't exist, just set primary_vdev_id, and return
SUCCESS, and don't config anything for dual sta.
2. If dual sta are not in MCC, don't send duty cycle percentage, return
SUCCESS.
Change-Id: Ib72033cf7d656e56c400759a7c5da13bf8d1377b
CRs-Fixed: 3009079
Currently the number of netdev interfaces created is equal to
the max number of vdev's supported. There shouldn't be a problem
w.r.t to adding the number of interfaces, the number of interfaces
which can active at a time is already controlled by the object
manager.
Remove the checks required to add the interfaces greater than
the max supported interfaces.
Change-Id: I5f9d1ca343788a77180a76f961fcc511feff4036
CRs-Fixed: 3010712
Host uses return value of function "hdd_get_adapter_home_channel" as
channel number when starting spectral scan and setting chainmask.
Which cause chainmask not to be set properly and parsing spectral
scan result fail. So, add this change to set chainmask based on home
channel frequency.
Change-Id: I3e25091841769d738dec101708e16602d783a363
CRs-Fixed: 3001325
Don't check for NULL for session in tdls_update_node_he_caps()
as the caller lim_process_sme_tdls_add_sta_req() is already
checking that.
Change-Id: I15b8144db385265fb77612f17123fd9f949ab7bf
CRs-Fixed: 3007560
Currently driver has only one name for an INI, with
this change add second name as well for few INIs based on
new requirement.
Change-Id: I6eee13935d1c5c74794027b88d94cbb572339e9e
CRs-Fixed: 3007209
Currently host driver supports only one ini file,
with this change add support for multiple ini files.
Change-Id: I6313f50a6275501d0694876f24b8d4a1ce6c2e72
CRs-Fixed: 3007190
As part of new implementation for 802.11BE MLD(multi link device)
address also need to be generated, derive the address during the
driver probe for max supported MLD's.
Change-Id: I092aac0607a6b7e9e420b1c82a61869cc0b8a2d4
CRs-Fixed: 2993460
hdd_assemble_rate_code uses WMI_ASSEMBLE_RATECODE_V1 to configure rate
to Fw. But this macro is not as per expectation by FW.
To address this, Don't use hdd_assemble_rate_code API and read the rate
code from user as per FW expectation and configure it to the FW.
To set 11be rate, write 2 bytes value to the sysfs entry as below.
In this byte-1 should be 11be preamble id i.e. 5, in byte-2 MSB 3-bits
represents NSS and LSB 5-bits represents MCS. For e.g. the below
command will configure the 11be rate to MCS 7 and NSS 2.
echo 0x0547 > /sys/class/net/wlan1/11be_rate
Change-Id: I9c8ecc840b14fbd954f0df1f8ec841daf5435fab
CRs-Fixed: 3004042
Currently, irrespective of OP MODE of the driver, the HOST sets
85th bit (Beacon Protection Enabled) in octet 11 of extended
capabilities. As per the 802.11 2020 standard, this field is
reserved for a non-AP STA.
The fix is to make sure 85th bit in octet 11 of extended
capabilities are reserved for a non-AP STA.
Change-Id: I36825bd8045af51d0f998ca5bcd90a3bc8dce632
CRs-Fixed: 2999299
Fill TDLS 6Ghz peer capability correctly in Add STA
so that carrect Peer capability should be sent in
Peer Assoc.
Change-Id: I3eb6c387286b86e07c33be4751501b356b24ff68
CRs-Fixed: 3008407
The RRM request may have different country code with DUT internal
regdb configure, use country code from beacon IE if it is present,
otherwise use internal country code to verify op class of neighbor
report channel list.
CRs-Fixed: 2997474
Change-Id: I35a62d9791f08d26dd8a892739612eb422805523
When firmware sends Roam synch indication, driver changes the
roam offload state to ROAM_INIT and after set key completion is
received, RSO start will be sent. But if EAP/EAPOL fails and
disconnection is triggered then deinit command is sent without
setting roam scan mode to 0 with RSO stop command.
So change roam offload state to RSO_STOPPED if auth status is
connected in roam synch indication.
Change-Id: If8f56ce48500f6848fa917854b6252f8deb67c01
CRs-Fixed: 3005697
Currently driver sends rsn caps to fw via
WMI_VDEV_PARAM_RSN_CAPABILITY without validation of ap
capability to support ocv which may cause issue during csa.
when ocv cap is set in vdev param, then fw does sa query and
may not get any data if ap doesn't support ocv which may lead
to disconnection.
Fix is to set ocv capability in rsn based on ap capability to
avoid unwanted disconnection.
Change-Id: I90f9ccffb00878592179a3159adee0b3199555a3
CRs-Fixed: 3008137
This reverts change Id8134003e6f7a3e0368b20c496f650e0b7025b9e
Moving cp stats to scheduler thread is breaking the
synchronization in stats collection. Currently, when a get stats
command is issued from framework, host driver sends the same to
firmware and wait for both llstats and get_station related stats.
The expectation is to receive get_stats first and then llstats.
Host driver has a wait for the last llstats event to return the
stats to userspace. As the cp stats(get_station stats) are moved
to scheduler thread, the order of these events can't be ensured
as llstats are still running in kworker thread. llstats event gets
processed before cp stats mostly and stats are returned
immediately to framework. Framework may issue the get stats
command again and the same is sent to firmware, which may result
in synchronization issue in firmware as well.
Moving llstats also to scheduler thread may not be optimal as these
are aggressive and can be queried by framework multiple times with
a milliseconds gap.
So, move back the cp stats to kworker thread to maintain
synchronization.
Change-Id: I8dc518f0de37e7cc203cb1f6e67045d74b304d93
CRs-Fixed: 3002534
Currently fw is allowed to provide ch_wr_ie len upto 20 bytes.
If fw provides ie len > 20 bytes then driver may lead to
access invalid memory. To find sub element, subelement len is
calculated from total len without any validation. ele may
point to invalid address when subelement which is calculated
from ie len becomes > len.
Fix is to compare ie len provided by fw with max ie len and
validate subelement len and then proceed with subelement.
Change-Id: I1a833c3828e4afc6e37ed27e008663152b6b5d86
CRs-Fixed: 2995818
