Currently host doesn't support below configuration for FW:
gEnable2x2=0 (disable 2x2 mode)
dual_mac_feature=0(ENABLE_DBS_CXN_AND_SCAN)
tx_chain_mask_2g=0x1
rx_chain_mask_2g=0x1
tx_chain_mask_5g=4
rx_chain_mask_5g=4
disable_rx_mrc_2g=1
disable_tx_mrc_2g=1
disable_tx_mrc_5g=1
disable_rx_mrc_5g=1
gSetTxChainmask1x1=0
gSetRxChainmask1x1=0
Now there is a new requirement for QCA6595:
1. RF chain0: WLAN 2.4G with 1x1 antenna
2. EF chain1: WLAN 5G with 1x1 antenna
3. RF chain1: BT 2.4G with 1x1 antenna
To support this new requirement, need to exclude the case in
condition check when gEnable2x2=0 and dual_mac_feature=0.
Change-Id: Ic08a4b7f5eb4beece867d7d7b4ae1796e67eae85
CRs-Fixed: 3074098
Update thermal mitigation policy table to fix the issue related to
thermal subcmd invoked from userspace
Change-Id: I5beb82d68253651736657d3131f4571e877d6042
CRs-Fixed: 3070375
Currently, driver is depending on NS frame to be received to configure
peer multicast address for an NDP session. If there is a delay in NS
frame reception, peer multicast address list will be configured to the
FW without actual peer multicast address. Because of this, FW will drop
the NS frame from NDP peer.
To address this, derive peer multicast address from peer MAC address
and include it in multicast address list that is configured to the FW.
Change-Id: I92a575352d592b4001dc4f061e31eb7f592f8445
CRs-Fixed: 3066990
Kbuild change to
- Disable timer irq for CE in WCN7850
- Disable status ring timer WAR in WCN7850
Change-Id: I59a247bf14450c5e1ec194c505f3a00eb5f3619f
CRs-Fixed: 3075871
Add support to send beacon received from firmware on STA interface
to mon interface based on management rx filters set by user in
vendor command.
Change-Id: I186ab0d697da831894854d7680265e82dd3adcef
CRs-Fixed: 3073478
Pass psoc ptr as argument in addition to existing args in
wlan_reg_get_6g_power_type_for_ctry API to support new APIs
like wlan_cm_get_check_6ghz_security that are invoked within.
Change-Id: I9615c5d2cb509a0c9f8e10073c0928ab38f179f8
CRs-Fixed: 3080203
Currently, Host is not caching the response status for the set HW mode
request. Without this status, it is difficult to debug HW mode mismatch
between host and FW when the logs are not available during the set HW
mode command.
To address this, cache the set HW mode response status.
Change-Id: I61b935d54648bc80901bfe7127227ffaa8d7cd7b
CRs-Fixed: 3076445
In packet capture component change enum pkt_capture_mode
from value to bit map.
Change-Id: Ic777b5091e85ed8c906d7e855b5cadb0fa3319d5
CRs-Fixed: 3048502
Add path of final version (E3.0 R38) of cleaned up HW header files
with comments removed and appropriate copyright added.
Change-Id: I5b65141d68672da6368f71132ad583ed1fc3db53
CRs-Fixed: 3076670
In security association scenario, if userspace gets notified about the
link peer first, it will cancel the connection because it doesn't
contain RSN IEs. Skip notifying userspace about this STA because it is
not needed.
Change-Id: I726583ade6d463bf7eed79d83afc0bcd1ae8192f
CRs-fixed: 3075695
For MLO connection, host will use MLD mac address as eapol
dest_mac address check condition, but currently the macro
used is not the right one, so the check always return failure
and RX eapol frame is dropped in SAP HDD.
Use right macro WLAN_FEATURE_11BE_MLO to enable this check
Change-Id: I5e9e265583d9c39899c6604f1a16bde2f08484a9
CRs-Fixed: 3074632
Spin_lock_bh is introduced in ipa wlan rx path by security fix
I0c0bc6e60efa193126ba1e3eca36c5e02f7f76a3,
wlan_ipa_w2i_cb->cdp_peer_state_get->dp_get_peer_state->
dp_peer_find_hash_find->qdf_spin_unlock_bh(&soc->peer_hash_lock),
which make rx pkt aggregation failed, for each rx pkt, once
put into backlog queue, net_rx soft irq is scheduled to handle it.
which make rx throughput failed to meet KPI.
TO avoid spin_lock_bh don't call cdp_peer_state_get for each rx pkt,
only call 1 time, and save peer auth state in IPA context, for following
pkts, just get peer auth state from IPA context without spin_lock_bh.
Change-Id: I36196bab4626194bda254219c4c44dc4f029cff0
CRs-Fixed: 3076978
Use CONFIG_SLUB_DEBUG_On to enable certain flags. This ensures that
these flags are not enabled for PERF builds.
Change-Id: I8c8e032ca1a0344f12fbad4dca543e333d601916
CRs-Fixed: 3045963
Set system PM_QOS with low latency only for "very-high" throughput levels
in TX case. Currently, its being done for "high" throughput levels.
In less than "very-high" throughput cases, this allows CPU cores to
enter low power modes. This is done only for non-offloaded packets e.g.
UDP.
Change-Id: Idf1dd2968b7dd8b4ef9f4061ee862de03d962c6e
CRs-Fixed: 3045963
Whenever a eapol packet is received over the control port driver
allocated using the qdf_nbuf_alloc and passes it over to the
hard_start_xmit which again tries to add the skb to the qdf nbuf
tracking list these operations result in the false positive warning
message of double allocation from the nbuf debug framework.
So, use the skb_alloc api instead of qdf_nbuf_alloc, so the skb
can be tracked in the hard_start_xmit and avoid the warning from
the debug framework
Change-Id: I7cdb54fa6ef49f313cfb5ff48221aaf742e18a1f
CRs-Fixed: 3079746
Current only TYPE_STATION_STATS is designed to be send
by qmi. and other request type should send by wmi.
if sending by qmi, qmi_get/qmi_put should be call to protect
qmi send and qmi response.
Change to check type and only allow TYPE_STATION_STATS to be
send by qmi.
Change-Id: I57b0bdb6717e259606993ea24ef024745a456664
CRs-Fixed: 3073744
Currently FW version sub ID is defined as 4-bits. But with new
requirement, the FW version sub ID value can vary up to 99.
To accommodate all possible values, increase number of bits to 7
for FW version sub ID.
Change-Id: I033697ba65d52b976658d795092fbff3b40faf9c
CRs-Fixed: 3067649
Dynamic GRO feature is enabled by default and aimed for specific
customers. Add an ini control to allow other customers to config
this feature enable/disable.
Change-Id: I83edd69d0e30d5944f0724ed8350328abff619bb
CRs-Fixed: 3070912
STA + STA DBS roaming rules are:
1. Roaming will be enabled on both interfaces.
2. Roaming bands are restricted to maintain only DBS.
While STA2 connection, the host sets VDEV level PCL for
vdev1 after association completion only and initializes
roam band mask after the 4-way handshake. So, when sending
PCL to FW value of roam band mask is 0, the host cannot
filter different band channels from STA2's PCL list.
This allows STA2 to roam to the different bands and violate
rule 2.
Fix is to make sure roaming bands are restricted to maintain
only DBS.
Change-Id: I1c9d2edb34f59e00c2fd14ea7894c324f9c64047
CRs-Fixed: 3075106
Currently for TX packets, TDLS packet accounting is taking place inline
with the transmit path. Move it to TX completion path as on high
throughputs, TX completion is relatively light-weight as compared to
transmit path.
CRs-Fixed: 3078062
Change-Id: Ib9a028e18c4945f3c92c1931e46ab6582aa51a9e
Currently, if the host receives the SETROAMBAND command in a
disconnected state, then the host returns an error to userspace.
As per the new requirement, the Host should store the value of
roam band mask irrespective of the connection state.
Change-Id: If1d59a35b04da5e4b66830803af619833e029af2
CRs-Fixed: 3076810
Enable config flag to use multiple tx and tx completion
ring pairs for qca6750 when IPA is disabled.
Change-Id: Ide99b2f4d912b3bca551438cba522c2f9366b5d2
CRs-Fixed: 3075385
In connectivity logging for ROAM RESULT log
bssid if ap type is Roamed AP in case of roaming
success and Current connected AP if roaming fails.
Also the vdev id field is not filled for mgmt frame
Tx and is always printed as 0.
Fill the vdev id for mgmt frame TX.
Change-Id: I7d6fe7ba47b508fadaf9b9872e644d8b737bf001
CRs-Fixed: 3068229
When vdev0 STA roamed to another channel, vdev1 SAP CSA for SCC
when ROAM_SYNCH_IN_PROG, will disable roam, but no RSO stop to F/W,
F/W RSO isn't disabled, but host vdev0 will enter RSO_STOPPED, host
F/W RSO state out of sync.
If vdev0 STA next roam sync come soon, it won't be handled for host
RSO_STOPPED, neither roam sync complete nor disconnect will happen,
F/W will asert after wait roam sync complete timeout.
To fix it, Only do SAP CSA check after roam complete and RSO
reenabled, can avoid host F/W RSO state out of sync issue.
Change-Id: I77ccf30cac38f62c6ef8330c6da00364249b242e
CRs-Fixed: 3076935
EAP length is of 2 bytes, but currently the attribute type
used is NLA_U8. This causes the EAP packets with length
greater than 255 to print invalid length.
For roam current AP, the roamed AP info is printed.
Use NLA_U16 attribute for the EAP length and fill
correct event type for the current connected AP.
Change-Id: I9b86055a4817163db17e469ca45b4a0044d5b2d6
CRs-Fixed: 3075012
