Added flag for HTT HTC tx based completion. currently
packet are freed using htt htc misc list.
Change-Id: I2e7e4d59cadf30f4bb14eaefc045240d1ebc1aaa
CRs-Fixed: 2922547
In wlan_hdd_validate_operation_channel, "status" is override
to QDF_STATUS_SUCCESS after "ucfg_mlme_get_sap_allow_all_channels"
call. Reset "status" to QDF_STATUS_E_INVAL before checking
with supported channel list, otherwise QDF_STATUS_SUCCESS
will be returned for unsupported channel case.
Change-Id: Ibc3396eb89634b0efc77262e90427510d26e0f39
CRs-Fixed: 2946475
When starting SAP, the power mode is set to VLP to comply with
regulatory rules. There is no need to set this when starting SAP in
2GHz or 5GHz bands, so restore the power mode back to LPI. This
allows any concurrent operations to work on the full channel list.
Change-Id: Ic6270d9cf3e20e544a3dbaf4db8bbe1d85753c83
CRs-fixed: 2942809
Currently channel switch command accepts only channel number as
parameter but with 6GHz changes channel switch can come for the
6GHz channel as well and to support 6GHz channel switch frequency
needs to be accepted as parameter.
To address above issue add support to accept frequency as
parameter for channel switch command.
Change-Id: I38978348c0d70e3e860d4644b4664f8775ecb777
CRs-Fixed: 2931485
num_transmit_power_env of tDot11fProbeResponse should also update like
tDot11fBeacon2, otherwise default value is 0, and transmit power
envelope IE(195) will not pack into probe response template.
Fix it by updating num_transmit_power_env of tDot11fProbeResponse to
same as tDot11fBeacon2.
Change-Id: I865ba9d9ad96068c52d3d6434b113cb7662e95c6
CRs-Fixed: 2933031
Fill he and vht parameters in data tx and rx packets for packet
capture mode to update in radio tap header.
Change-Id: I229fc41657456b9ab5d8a2dfce1cdd039b624fcb
CRs-Fixed: 2942108
Currently centre frequency filled in data rx packets for packet
capture mode. Need to fill base frequency so filling frequency
from connection policy manager.
Change-Id: I79abe4e8a27a853c156eff8618be2f280fc54e78
CRs-Fixed: 2942107
When updating the scan filter with valid channels, refer to the MLME
channel list instead of the policy manager list. The policy manager list
is used mainly for SAP related APIs.
Change-Id: I5530e5bcfd6b5c04063d7530fbc996ffca91df3f
CRs-fixed: 2946365
Firmare sends SAP TWT teardown event to host. Host handle
the event and send values to userspace via nl layer
Change-Id: I714c6a18399c1e0d8b79d31af984037f2f5e2024
CRs-Fixed: 2938332
Peer mac address is required in SAP mode TWT events.
So add support to send mac_address attribute in all
the TWT events to userspace.
Change-Id: Iab7c210eb2a058315b71f2327e6ac07d97ea7200
CRs-Fixed: 2940862
In host, add support to handle the SAP TWT setup event
and sends the event to userspace via nl layer
Change-Id: I8614e76a28f7b0af0146e3fe8553b24212b7991b
CRs-Fixed: 2938086
In host, add support to handle SAP TWT pause/resume/nudge
event and sends the event to userspace via nl layer
Change-Id: I319cb7c67ffc2f8db284a737ca94f7d746ffe27f
CRs-Fixed: 2938335
In any start BSS or ACS related function, change the calls to regulatory
to access the secondary channel list instead. This list will hold the
VLP channels specifically for any beaconing modes. This allows a client
and an AP to operate simultaneously on different power modes.
Change-Id: Ic06b408ebcc78292d84f1f035c00bf39a23de3ca
CRs-fixed: 2944484
Add a sanity check to validate the Tx chainmask value
sent from the user space for each HW mode.
Change-Id: I2705efe20fcb13bf8343088ceecb4207e2562789
CRs-Fixed: 2943363
When vht cap indicates the vht max MPDU size >= 7991 supported,
ht cap A-MSDU length field should indicate 7935 octets
supported according to 80211 specification.
At present no WMI HT cap defined for ht cap A-MSDU length field
from target.
Fix the issue by override ht amsdu len to 1 if vht max mpdu
len >= 7991 supported by target.
Change-Id: I9d2b8c11e7a27e016f618c1a2c8a380d081a6ba7
CRs-Fixed: 2929148
When roaming/roam sync is in progress, the host receives a "disable
fast roaming" indication from the supplicant. Host process roaming
or roam sync indication in schedular thread and process disable
fast roaming process is in a supplicant thread. As both processes
are executed in different threads, there is a possibility in the
host that the roaming state gets changes from ROAM_SYNCH_IN_PROG
to RSO_STOPPED or ROAMING_IN_PROG to RSO_STOPPED in the middle of
roaming.
A state change in the middle of roaming can lead to multiple
issues.
To avoid this host should not process disable roaming indication
from userspace, if roaming is in progress.
Change-Id: I9b02683eab7db9b5be12ada6d922073e5267b8a5
CRs-Fixed: 2944303
CNSS platform will notify bus related event, and add related
handler in CLD driver.
Change-Id: I257f2e09c4fbefa6c4913eb7a7deba165a9b73ec
CRs-Fixed: 2922102
Increase ce_service_max_yield_time to 2 msec in SLUB_DEBUG
builds for helium SNOC platforms to improve the CE reaping
performance.
Change-Id: I2a8a21fd1a65bc2ffc5fb17986116613f47510c7
CRs-Fixed: 2937231
TWT notify event from firmware is expected only if the teardown
is initiated by the firmware during scenarios like
(roaming in progress, etc).
If the TWT teardown is initiated by the peer then notify WMI event
is not expected from the firmware.
Change-Id: Ic13a4858fb06d023d5e71da10320a546a1dcf80d
CRs-Fixed: 2944663
Sometimes we need PDEV suspend mode, WMI_PDEV_SUSPEND_CMDID and
WMI_PDEV_RESUME_CMDID. But currently design, only support WoW
suspend or not support two choices. And, there are two confused
ini configuration, gDisableWow and gEnableWoW.
1. Add new ini gSuspendMode to set suspend mode. Default 2.
0, does not support suspend
1, legency pdev suspend mode
2, WoW suspend mode
2. Clean gDisableWow. It is replaced by gSuspendMode=0.
HDD suspend/resume function get the value by new API
ucfg_pmo_get_suspend_mode().
Change-Id: Icbeef3df6879ca2054f64e0292e9b9469c4936d4
CRs-fixed: 2940788
The INI skip_tpe_consideration when set, skips power from AP's
TPE IE in TPC power calculation for 2.4G/5G case. Enable this
INI by default since APs advertise low TPE powers for IoT, thus
lowering overall TPC power.
Change-Id: I6c07bbd684579c2fa3617e49d76c75b5bf3f2815
CRs-Fixed: 2941630
Fragments are not flushed as part of rekey which
could result in fragments encrypted under different
keys to be reassembled.
Fix is to flush fragments for the peer for which add
key request is received.
Change-Id: I0c018ff7375272125c62aaea7b8ad4df9e842508
CRs-Fixed: 2875950
wma_send_peer_assoc() calls wma_unified_peer_state_update() which
always sets the peer state as AUTH irrespective of peer state.
Remove wma_unified_peer_state_update() from wma_send_peer_assoc()
to handle peer state.
Change-Id: I4a887acbc8018653c34b927636cce7cc05323838
CRs-Fixed: 2888808
For some of the stability issues triggered by H.W,
by the time host detects it most of the QDF history
is getting overwritten to avoid this increasing QDF
nbuf history. So that there will be less chance of
events getting overwritten.
Change-Id: Ia4bad1a175976af2e56126b56ae8c92a988e4289
CRs-Fixed: 2942868