The Android Common Kernel (ACK) accepted change [1] to 5.10.20 which
enables support for nested composite objects in the Kbuild
system. This was introduced to fix the "Argument list too long" error
that can occur when there are too many filenames passed by the build
system to the "ar" command.
The expectation at that time was that this patch would be maintained
for all future ACK kernels. However the ACK maintenance team has
decided not to maintain this patch beyond the 5.10 kernel, so update
the logic that determines if an ACK kernel has support for the
feature.
Subsequent changes will need to be made to address the "Argument list
too long" error when using an ACK that does not have this support.
[1] 21c713f8e8
Change-Id: Ief9a74a24d58796a90e19bd86fa269e64bcf4c73
CRs-Fixed: 3139401
(1) is_critical pointer flag in hdd_wmm_classify_pkt is not referred
properly which then hdd_wmm_get_user_priority_from_ip_tos() is skipped.
(2) CONFIG_WLAN_CUSTOM_DSCP_UP_MAP is only configured when
CONFIG_REMOVE_PKT_LOG is 'n', so if CONFIG_REMOVE_PKT_LOG is set to 'y',
CONFIG_WLAN_CUSTOM_DSCP_UP_MAP will no chance to be enabled,
then hdd_custom_dscp_up_map() dummy function is invoked always.
CONFIG_WLAN_CUSTOM_DSCP_UP_MAP should not be tied with
CONFIG_REMOVE_PKT_LOG, move it out of CONFIG_REMOVE_PKT_LOG,
also fix is_critical flag referring issue.
Change-Id: Iac6e7ccb41270677298d152498ad7a9c0c66ff14
CRs-Fixed: 3205745
Currently when sar safety unsolited timer expires, driver schedules
a work to send sar safety unsolited events to user space. When driver
receives sar set command from user space it tries to stop this work
with delayed work stop sync. This delayed work stop sync API waits for
work to get complete and then it stops the work, because of this,
work runs the complete for loop and sends extra sar safety unsolicited
events even after receiving sar set command.
To addrerss above issue, set the sar safety request response event
before delayed work stop sync to complete the work.
Change-Id: I3485e4b1ea600393ff2d9512a055de92d0a3d612
CRs-Fixed: 3213334
As part of protected dynamic interface control feature,
if the user space disables WiFi, then the platform driver
disables the WLAN HW as well. Until the user enables WiFi,
the WLAN HW stays disabled.
So, add support to enable the WLAN HW, when the WiFi is
enabled by user space.
Change-Id: If6b90ae57c4471f4c613ead8310fd0a7ada818f3
CRs-Fixed: 3215335
Limit mlo link num and band by psoc sta cfg mlo_support_link_num and
mlo_support_link_band.
If mlo_support_link_num is 1, only permit 1 mlo link, don't permit
partner link.
Disable both assoc link and partner link on disallowed band too.
Change-Id: I04f0725ceb0fb4e0bd14ca44ff1a870702b62285
CRs-Fixed: 3211973
Add cfg to configure the max number of links supported for mlo sta
connection.
Add cfg to configure the band bitmap that mlo sta connection supports.
Change-Id: I6b27a7eb13eff026c5123e4bd24ba2424dba781d
CRs-Fixed: 3202029
Currently target_if_cp_stats_extract_vdev_summary_stats
function prints bcn SNR which can be RSSI as well based on
whether firmware supports reporting rssi or not.
Add check for firware support to print RSSI/SNR
Change-Id: Ifef7bfad7d79c1a1bb84641bc1d3632f6d683252
CRs-Fixed: 3209907
In api wlan_cm_is_roam_sync_in_progress(), the roam_sync
status is checked for every instance of
wlan_cm_is_roam_sync_in_progress resulting in excessive
printing of cm_is_vdev_roam_sync_inprogress logs
Add check to verify roam_sync status for STA mode which
results in trimming of cm_is_vdev_roam_sync_inprogress()
logs.
Change-Id: If0228edb90d718c7fde2b8f34e0003256cfd139b
CRs-Fixed: 3211915
This is about SAP+SAP+STA case. Restart third SAP failed after start
up and then 5/6 GHz disabled. This change allows SAP+SAP+STA SCC on
same mac and avoid third SAP restart fail.
Change-Id: I691b2e03132acfb8f724fc2f75b3816d17eb4d17
CRs-Fixed: 3198977
In hw mode change offload case, update the mac id and
frequency range in hw mode transition event handler
instead of post msg to lim and sme to avoid the
information updating delay.
Change-Id: I3dc1d37880691148c4cffd8e1f5d46172f03cb0d
CRs-Fixed: 3211683
For targets not supporting shadow config v3, the compilation
may fail since the definition for shadow config v3 will not
be available.
Featurize the shadow config v3 properly to avoid any
compilation errors for targets not supporting this feature.
Change-Id: I6d968ff98776159319ec5edad1ada1b6d888f87e
CRs-Fixed: 3214412
Start one SAP on 5 GHz and one SAP on 2 GHz, and start third SAP with ACS
on 2 GHz band. Then, 3 SAP have different freq_seg0 after disable 5 GHz and
6 GHz band. Raise this change to check AP_AP SCC override with freq_seg0
and freq_seg1.
Change-Id: I720aff19a20e3d5ab9a2a31246e47308f7d09d0e
CRs-Fixed: 3165082
Currently EHT IE is sent with contents 0, fix is
to send read EHT IE info from mlme config if session
is NULL.
Change-Id: I7da0d98c2ef7b34ee50d306a95fa7c80e9a5739a
CRs-Fixed: 3207350
Vendor commands of wiphy aren't initialized when driver load as FTM mode,
if changed to mission mode later with following cli:
echo 0 > /sys/module/wlan/parameters/con_mode,
vendor commands of wiphy keep uninitialized, wpa supplicant can't get
roam offload status by QCA_NL80211_VENDOR_SUBCMD_GET_SUPPORTED_FEATURES,
so PMK isn't sent to driver/firmware, roam offload failed.
To fix it, remove QDF_GLOBAL_FTM_MODE check in wlan_hdd_cfg80211_init, let
vendor commands of wiphy initialized in FTM mode too when driver load.
But in each vendor cmd, check FTM mode when called, if FTM mode, return
-EPERM.
When driver is changed to mission mode, all interfaces are deleted and
re-added by driver, when interface added event is received by
wpa supplicant, QCA_NL80211_VENDOR_SUBCMD_GET_SUPPORTED_FEATURES is
called again to get roam offload enabled status, PMK will be sent to
driver and firmware when RSO start, roam offload will work.
Change-Id: Ie0c868ebd4b7e356d72a154206b13df94f378188
CRs-Fixed: 3213221
Add config file for Mango WLAN device and enable emulation flag for
Mango WLAN device.
In addition, use static symbolic link '.mango -> .' for multi-ko support.
Change-Id: I0cebf11407e5625fd6475723496b9cda72cf5165
CRs-Fixed: 3210120
When sending Association request frame, include
MLD capabilities in basic variant multi link ie.
Change-Id: I07b9214a450e8f9cbfc7b0720cd4aab36498bc6c
CRs-Fixed: 3212101
In MLO connection, MLO AP is operating in country US domain and sending
op class and channel number based on global opclass. Due to which,
MLO sta is failed to get the channel freq because driver is checking
in the US domain list only.
Fix is, if freq is present in the particular domain then use it
or else check in global domain.
Change-Id: If376405c4c57c2c84028952f000abf45759ba316
CRs-Fixed: 3212004
Currently in beacon, assoc req and assoc resp
frames, MLO IE MLD cap present bit is set to 1
without filling the MLD cap subfields in MLO IE.
Fix, in Presence bitmap subfield of the Basic
Multi-Link element set MLD cap present bit as 0
if MLD cap subfiled is not present.
Change-Id: I676c887edd7198bb5178e09e58f6b24dbaa857a7
CRs-Fixed: 3197313
Currently locally generated vdev_id is passed to update
concurrency like to re-enable disabled sta link on one
p2p/sap down or handle concurrency on one ml sta link
down. This locally generated vdev id will be invalid/255
in case mode is non-sta, so hanlding will be done for non-sta
link down only.
Fix is to change vdev_id to session_id, so that session which
is deceremented due to session down can be provided and concurrency
handling can be done based on that.
Change-Id: Iaca9a339abbab3f5dab01e2224c3acd87df5bc0a
CRs-Fixed: 3212661
Currently if SCC frequencies are added in pcl list and
rest 5GHz frequencies are required to be added with lesser
weightage then all 5GHz/6GHz frequencies are added including
SCC channels. so in pcl duplicate entries are found for SCC
frequencies with different weightage.
Fix is not to add SCC frequencies during addition of 5GHz/6GHz
frequencies if SCC frequencies are already present in pcl.
Change-Id: I03123e4bf8caee62b0fcd0c3ae78d6cd7187c7de
CRs-Fixed: 3209858
The WAPI IE is not included in the probe response in the driver for
the WAPI SAP mode, and will cause the external WAPI STA does not
trigger the WAPI connection to the WAPI SAP if configured as WAPI
SAP mode.
Change-Id: I9212e0fe9d495e8300a2bfbed65d398e0fb27170
CRs-Fixed: 3148702
The dynamic GRO enable/disable based on ingress filters
should currently is restricted only to standalone STA.
This was done to address issue where ingress filters are
added on STA interface whenever SAP is up disabling GRO
unnecessarily.
Fix is to allow dynamic GRO to work on all interfaces
and concurrency scenarios based on the priority of
the ingress filter configured to avoid unnecessary
GRO disable in STA+SAP.
Change-Id: I1742f4539353939e3a40ff4096b3f833f2029b12
CRs-Fixed: 3206815
Currently, when driver receives connect request on secondary STA,
it checks if the secondary STA channel and first STA channel are
on different band to allow. This works fine for DBS solutions but
SBS solutions support same band(5GHz) channels on different MACs.
So, check if the secondary STA channel is on different mac to
allow connection.
Change-Id: If9cfe0f4605e31ab54b38a85fb9d38e9ca65871d
CRs-Fixed: 3212686
After the connection is established with HE160/VHT160 AP,
the STA downgrades the channel width to VHT80/HE80, leading
to 50% TPUT reduction.
The associated beacon processing doesn't consider the new VHT OP
IE definition while parsing the channel width. Fix the channel
width processing in the beacon processing.
Change-Id: Icd7d36a8352be7574474fb5f37fa9b4ca291aa04
CRs-Fixed: 3211833
Platform driver needs driver mode information to load different fw iamge,
so enables this mode exporting feature in wlan driver, also update
corret mode when mode change triggered from sysfs.
Change-Id: I848309440fdffd6517463e18190c03c1b7ed9269
CRs-Fixed: 3204663
Driver checks all 160Mhz 5 GHz SAP as DFS channel SAP, but
it is not right for some regdomain which no DFS required for
some 160 Mhz channels.
Fix by check wlan_reg_get_bonded_channel_state_for_freq API
to set DFS flag.
Change-Id: I8cd402c285e858ef8d322fc8d7cfaa32ae4c2056
CRs-Fixed: 3208538
