Currently driver updates the WTC global parameters irrespective
of the WTC attributes present in the vendor command.
This causes the WTC parameters to be reset and WTC roam
trigger doesn't happen.
For example, with below sequence of commands:
wpa_cli DRIVER setwtcmode 0 1 -40 -95 -90 -85
wpa_cli DRIVER ADDROAMSCANFREQUENCIES_LEGACY 19 2412 2417 2422
The WTC parameters TLV is not included in the RSO
update command.
Update the WTC params only if the WTC attribute is present.
Change-Id: I53e5d934368169069dbf059335859936d320aa4e
CRs-Fixed: 2954458
Currently in WTC mode the candidate AP RSSI threshold
configuration is applied for candidates on all band.
Add support to configure the candidate AP RSSI threshold for
different bands.
Change-Id: I94442c0f1bd3ea20dc2f5ebe893a9ead7fb8d890
CRs-Fixed: 2951610
Check the configured IOT OUIs in Beacon/Probe Response
IEs, but not in Associate Response IEs, because some APs
won't add its specific OUI in Associate Response frame.
Change-Id: I3aedeef0a5dbecd4bed41eb47a9374e654509746
CRs-Fixed: 2955964
When roaming to 160M AP by LFR3, host will update BSS info after
received roam sync event from firmware, but 160M isn't considered
when calculate channel width.
Actually vht_op->chanWidth alone cannot decide the actual BW, we need to
check difference of center_freq0 and center_freq1 to decide 160/80+80 or
80 if vht_op->chanWidth is 1.
Fix it by copying ft_session->ch_width to BSS info which covered 160M
channel width.
Change-Id: Ic4a992acfce186f7248dcc99d0c7b44ce38f099b
CRs-Fixed: 2954900
When thermal level higher than MITIGATION, TX will be
throttled completely.
Report DIAG event to notify user-space explicitly.
Change-Id: Ic2d8adfb6810ad03f3ec3b0847a176b694ace33a
CRs-Fixed: 2922102
The peer map v2 set in the target resource config
is sent to FW via WMI INIT CMD.
This configuration will enable index based AST
search in WDS mode.
CRs-Fixed: 2951231
Change-Id: If1c47c710832ddd46d99bffc66fc09e4fe76eab1
Currently, the same twt disable api hdd_send_twt_disable_cmd()
sends to firmware for both requestor and responder role.
As part of this change, decouple disable api based on requestor
and responder role as per below:
for requestor: hdd_send_twt_requestor_disable_cmd()
for responder: hdd_send_twt_responder_disable_cmd()
Change-Id: Ib92b0fa46dde78dec0d5b7ca914d018c7c0970e5
CRs-Fixed: 2937591
1. Currently, the same twt enable api hdd_send_twt_enable_cmd()
sends to firmware for both requestor and responder role.
2. When firmware receives enable command, it will be busy to
handle that command. If any back to back enable command, it can
lead to some issues.
As part of this change, decouple enable api based on requestor
and responder role as per below:
for requestor: hdd_send_twt_requestor_enable_cmd()
for responder: hdd_send_twt_responder_enable_cmd()
Synchronize twt enable command to avoid back to back command
issue.
Change-Id: I3d3840740fee7413d6123ece919c42558e9b35d1
CRs-Fixed: 2937540
Add support to dynamically control rx aggregation based
on clsact ingress filter addition or deletion. Disable
GRO/FISA when the filter is configured and enable GRO/FISA
back when there is no filter configured.
Change-Id: I462f62edf0acd191b57f40800118567edb2ac82d
CRs-Fixed: 2952276
If 2.4G 40MHz is disabled by channel bond mode ini -
gChannelBondingMode24GHz, override 2.4G ACS result
to 20Mhz channel width. Otherwise hostapd will
start ap failed on 40Mhz channel because the HE cap
has no 40Mhz bw supported.
Change-Id: I943621bf847491983f0654f7ae495fc970114575
CRs-Fixed: 2951620
1\ Since (rx_clear_count_delta - tx_frame_count_delta) * 100 maybe
overflow if rx_clear_count_delta and tx_frame_count_delta are uint32.
To resolve this issue, change uint32 to uint64.
2\ Since the previous data does not reset, then enable the congestion
feature again. It uses the old data and causes overflow.
Change-Id: I1c7d5f5be901e14424a70dd2931acb2175598199
CRs-Fixed: 2943725
Currently, reg_wifi_band enum is compared with
enum band_info. different values may lead to
invalid chan mode.
Fix is to compare reg_wifi_band with reg_wifi_band
enum value only.
Change-Id: Ibbe83ab5a8a428528bbeb28c941552a6f412a844
CRs-Fixed: 2949501
Currently host is sending noise floor as 0, even if channel info
event is not received from FW. This is stopping user space derive
noise floor information from other parameters like bandwidth.
To address this, do not set SURVEY_INFO_NOISE_DBM flag if the
noise floor is 0.
Change-Id: Icffdde6bce762c750200b4f1eefd17818780150e
CRs-Fixed: 2949905
Currently, hdd_vdev_destroy checks if any vdev is actively using
DBS while cleaning up the vdev. It stops the timer and sends set
hw_mode command to firmware to set the hw_mode to SMM if no vdev
is using DBS.
This causes delay in p2p interface down in below scenario,
1. Bring up both sta and p2p vdevs.
2. Initiate connection on sta to an AP which has both 2GHz and
5GHz candidates. hw_mode would be set to DBS as one of the
candidate is 2GHz.
3. Connection would be attempted first on 5GHz candidate if the
5GHz candidate score is good.
4. If p2p interface is disabled while sta connection is happening,
it stops the opportunistic timer and sets the hw_mode to SMM.
But the command would be waiting in serialization queue as
connect command is active currently. This is a blocking call
and userspace thread would be stuck till connection completion/
connection timeout(5 seconds) happens.
The above wait results delay in p2p down which in turn results
delay in wifi turn-on(as p2p down+set random mac+p2p up happens
as part of wifi turn on) and turn-off.
Don't set the hw_mode to SMM in this case as the sta connection
is in progress.
Change-Id: If286fe9bd9906eba71686cf1d50880aa065cc100
CRs-Fixed: 2926272
Update Country IE population API so that SAP uses secondary current
channel list instead of primary, to advertise correct number of
6G channels.
One other change is in TPC power calculation API, to add STA role
check along with lim join req check, since the API was returning
without calculation for SAP.
Change-Id: I3fafe252b119a5b58f5382fcbff60eb4c19688c6
CRs-Fixed: 2946474
wma_needShutdown related code is now obselete, during the cds_preenable
failure, this is obselete code is being invoked which is setting
wma->needShutdown. If the same is set the wma_close will not be
inokved resulting in the reference leak of of pdev object.
Remove obselete wma_needShutdown code.
Change-Id: Ia1463c9197593165eb5844e154f78fe3fe278fbd
CRs-Fixed: 2947133
Update the driver implementation to support generation and parsing of
information elements corresponding to max channel switch time.
Change-Id: Icaf3d1ceb17972da13e0cd0510fa952fac5c0f45
CRs-Fixed: 2941960
Currently, in the DP RX thread packet drop logic, the aggregated
packet as a whole is considered as one single packet. An aggregated
packet can hold anywhere between 2-16 packets, considering it as
a single packet will make the entire drop logic incorrect.
Consider all packets in the aggregate while computing the number of
enqueues & dequeues to fix the problem.
Change-Id: I70e65bcdfdbaf7821b36606ac6eeae61eaca7406
CRs-Fixed: 2948104
Vendor name is mentioned in the below fix to address an
interoperability issue with the specified make and model,
commit:I0d205e0833b2638aab15401bacdef7a0696d40c2
But specifying the vendor name is not allowed as nothing from
this fix/feature is authorized by the vendor.
So, remove the vendor name from the comment section.
Change-Id: Ib5839667dc1809a57ab54169e5506080b977da63
CRs-Fixed: 2948503
In PE session, host updates supported rates from beacon IE stored
in BSS descriptor. If OFDM rates are present in beacon while
operating frequency is not from 5GHz band, host copies them into
PE session's supported rated.
Hence add a check to avoid adding OFDM rates while operating
frequency is not 5GHz.
Change-Id: Ia3b39b31269b79e6d1f96d3a0bddb185597c0303
CRs-Fixed: 2948058
Add OCI IE in SA Query request, if host and the peer both OCV capable.
If both host and peer are OCV capable and host doesn't add OCI IE SA
Query request, peer fails to send SA query response that leads to
disconnection.
Change-Id: I734a4bea04dbe2126082e4e514b9865d33575fd0
CRs-Fixed: 2946244
Add support for TWT get_status command in SAP
As part of this change, TWT get_status command is supported
if
1. If particular dialog_id and particular mac_addr are
present
2. If dialog_id = 0 and particular mac_addr are present
3. If no parameter present
Change-Id: I5ce1719da7f9a3988ba6e1f04455a06faf9687c6
CRs-Fixed: 2937999
