Currently there is no support to enable NAN on indoor channels,
as per the new requirement add an ini support to enable NAN on
indoor channels.
Change-Id: Ia3acbc133cab4865d8ad69992e893be91439f50f
CRs-Fixed: 2943668
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
Currently, there is no panic when there is a net dev reference
leak. To catch the reference leak at the early stage, trigger
panic immediately after reference leak is detected.
Change-Id: Icbdd090dab50c8f695b5354c405f0506adce119d
CRs-Fixed: 2911563
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
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
For reassociate case, when disconnect is triggered by
wlan_hdd_try_disconnect, then disconnect event is not
indicated to kernel in disconnect handler -
hdd_dis_connect_handler. And if the csr_roam_connect
get failure for some reason, the kernel will only get
error code from driver connect request interface and
the connected bss information in kernel will not get
cleared. Then kernel / driver will be out of sync.
To fix that, for such csr_roam_connect failure case,
let driver return successful status code from driver
connect interface and indicate connection result failure
event to kernel to clear kernel bss information.
Change-Id: I5367262751e63c04553deeb7607cbe13c70f8e15
CRs-Fixed: 2940994
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
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
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
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
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
The following are the firmware expectations for the parameters
through p2p_set_noa:
If count > 1 , the duration should be smaller than interval.
If count = 1, the duration can be same or smaller as interval.
Hence, set the duration as interval if it is configured
greater than interval.
This commit adds the checks accordingly.
Fails the command if the above conditions do not pass.
Change-Id: Ic273b0167c3551cd4b21d4c6dc7f31ba5329bebc
CRs-Fixed: 2941170
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
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
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
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
If the retry count is more than zero then set the retry flag in
frame control of tx data packets in packet capture mode.
Change-Id: Ie1ecfc30c30946d97c92ee2612c825f8d3539f25
CRs-Fixed: 2932130
Transmit count received in tx completion status includes the success
transmission also, so retry count will be one less than transmit
count.
Change-Id: I81a06d4800b2f1015e618938229b7d7abfe5ed2e
CRs-Fixed: 2932141
Register for management control frames with the mgmt txrx
component in packet capture mode.
Change-Id: Ibaa20e00753cdeb6a15a79bd458166b47652cdb5
CRs-Fixed: 2932144
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
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
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
