add CONFIG_QCN7605_PCIE_GOLBAL_RESET_SUPPORT
which is used to support Genoa Pcie Global Reset
this feature only used for 3rd party platform
which do not support hardware reset by toogle WLAN_EN pin
Change-Id: I0fa356e362ebafe18378e0a803bf3f4a00c77628
A race condition is observed when runtime suspend is aborted
due to pending TX packets but context switch happened and pm_state
did not revert to active state yet. In parallel, WMI_PEER_DELETE
command is queued but not sent as pm_state is still in suspending
state.
To fix this, schedule HTC queue kicker work to resend pending
commands again after dp_runtime_suspend aborts due
to pending TX packets.
Change-Id: I6d2c4140a4635c0aec304f48b15fb2b539ac39ea
CRs-Fixed: 2813657
In case of STA + SAP/GO, Driver fist disable roaming on all
adapters before bss start and enable roaming after start bss
(SAP/GO) in case of failure/success.
Due to commit I4870c69a0e0ca1e8cad734a591f09e402b7a32fa,
Driver fails to re-enable roaming after failure/success
of SAP/GO process.
Fix is to enable roaming after start bss in case of
failure/success.
Change-Id: Ibe90f0685f41984a5841859ea96834f7760ff9a1
CRs-Fixed: 2811306
Currently the adapter features update work is created only
for the STA types of interfaces, since this feature is only
used for STA mode. But this can cause an issue when a SAP
interface is changed to STA runtime, since the workqueue will
not be initialized (since create adapter was of SAP type) but
it will be attempted to be destroyed (since the adapter is of
STA type) during the cleanup of adapter.
The creation/destruction of this workqueue cannot be done
in the start/stop adapter, since the rtnl lock will be held
during this operation and the cancelling of the adapter features
workqueue can cause it to wait on rtnl lock, leading to a
possible scenario of a deadlock.
Hence as a mitigation for this issue, we create the adapter
features update workqueue for all the interfaces and clean it
up for all the interfaces as well.
Change-Id: I598480e9f248f50e46764f7f32b876a8efaeee8d
CRs-Fixed: 2811934
Currently the driver does not have a support to
filter out the 6ghz frequencies from the valid freq
list, and hence there is a high chance of selecting
the 6ghz freq as an operating freq for SAP, which
the legacy clients won't be able to scan.
Fix is to add a support for filtering out the 6ghz
frequencies from the valid freq list.
Change-Id: I3c32b4c8c5b93eae04d49d2d5b6bd4ec9852c2a9
CRs-Fixed: 2808350
Prior to the kernel version4.7 struct ieee80211_channel used enum
ieee80211_band. Beginning with kernel version4.7 struct ieee80211_channel
use enum nl80211_band. So there is an issue of typecasting of the channel
band parameter.
To resolve the above issue a helper function is added to typecast the band
parameter according to the kernel version.
Change-Id: I1af692bb7cae5ab2e71556128ce672c6b145f92f
CRs-Fixed: 2815201
As part of power optimization to club LL and get stats request add
a debug log to indicate when cached get station stats is getting
returned to user space.
Change-Id: Id1f80e1589c1913d0129b435cd2bdbd807800230
CRs-Fixed: 2814701
Currently if peer client supports the MCS12 and
MCS13 support in assoc request then also DUT(as SAP)
is not sending the QCN IE in assoc response.
This results into the low Tput as peer client uses
only rates till MCS11.
To fix this issue, send the QCN IE with MCS12 and
MCS13 support in assoc response if peer client
supports it.
CRs-Fixed: 2814863
Change-Id: I17c16705b5a015e1dd22849212a19365ac78acaa
cds_get_context() function already takes care of logging the
caller function name in case of any error.
Hence there is no need to add the error log again.
Getting rid of these unnecessary logs reduces driver memory footprint.
CRs-Fixed: 2814480
Change-Id: I1459d7af76b19614775e0a5b0982a2ca0fbdb935
cds_get_context() function already takes care of logging the
caller function name in case of any error.
Hence there is no need to add the error log again.
Getting rid of these unnecessary logs reduces driver memory footprint.
CRs-Fixed: 2814471
Change-Id: I70351edc06db00171270369a91589b0d9409f70a
cds_get_context() function already takes care of logging the
caller function name in case of any error.
Hence there is no need to add the error log again.
Getting rid of these unnecessary logs reduces driver memory footprint.
CRs-Fixed: 2813747
Change-Id: I025b5882f86b0b9f52e5ac903b873c06c458d07c
When host receives ap capability change indication,
internal disconnection is triggered from csr without
sending stop roaming (RSO stop) to fw. So in STA+STA
scenario, after connection on 1st sta, roaming will
be enabled on 2nd sta, but since RSO stop was not sent
on 1st sta, firmware will assert as btm offload is not
disabled at the 1st STA.
Disable roaming first, followed by vdev stop/vdev down to
firmware.
Change-Id: I183b590b36ecfd81150bb59c33c4752c718c93ba
CRs-Fixed: 2798081
Currently for ll stats host fill country information from
mac context which is not updated with latest country information.
To address above issue use correct api to fill country info
for ll stats.
Change-Id: I744b172cf935e44568b9ee902a97275887e45001
CRs-Fixed: 2805196
The event WMI_ROAM_STATS_EVENTID is received after
every roam, once the roam synch complete is sent by the host.
This event contains details regarding the btm response.
This helps to debug the scenario when roam failure happen.
Print the info received related to roam scan type & roam status
info into kmsg.
Change-Id: Idd688eb4d1e699573fa1e243873c30ffdc5bf96f
CRs-Fixed: 2794555
In FISA path number of list elements in head nbuf is not updated,
leading to wrong calculation of dp thread stats and packets are dropped.
Update the number of list elements in head nbuf before flush.
During calculation of outstanding packets to be processed
by dp rx thread take rx flushed packets into consideration.
Change-Id: Id96ceee71e035fdbe17f0da4b662c6f848296fbd
CRs-Fixed: 2811001
In order to improve the hang data it will be now processed internally
on every dump, hence store the data in the global variable to get
parsed by tools internally.
Change-Id: I0cfacd0643e5e486630a8ba0989c0d7d0c9a63c8
CRs-Fixed: 2810338
New files are created for 6ghz scan functionality. Add the same
for compilation.
Change-Id: I3f715db50fb5020afea74297794d07ddc5b39913
CRs-Fixed: 2806415
Currently net_device is being validated inside the
hdd_for_each_adapter_dev_held_safe loop. This is not required as
hdd_for_each_adapter_dev_held_safe will hold the reference for
net_device and prevent it from being deleted. So net_device validation
is not required inside hdd_for_each_adapter_dev_held_safe loop.
Change-Id: Id7e78748b80e7a3bbe50fee43a28fd0d48bd6856
CRs-Fixed: 2812716
Currently driver has parse_mac_trace cmm script which is
not updated for long time. There are many modules which were
added and many new messages were added and some of the
messages were removed.
Update the script according to current code.
Change-Id: I87bfe7fe74e73ccdc63b52ed6b96e163d214bb57
CRs-Fixed: 2810396
Currently, driver doesn't print STA info before passing it to the
kernel. This is making difficult to debug the STA disconnection
issues.
To address this, print sta info before giving to the kernel.
Change-Id: I8346bc489bfa3ca88b307fcb8d5cd4691ca8fe0d
CRs-Fixed: 2791922
Some IOT APs set supported rates to zero in probe response. Host uses
probe response/beacon to update scan cache. Host uses supported rates
from scan cache to update in assoc request.
As the supported rates in probe response are zeros, host doesn't
add supported rate IE in assoc request which leads to association
failure. Hence add BSS basic rates in assoc request if supported
rates in scan cache is not present.
Change-Id: I1eb56f437c39494f386e7c97aac4b4bc56b156c8
CRs-Fixed: 2813072
Previously, if STA is connected to DFS channel and SAP starts on
Non-DBS HW, then it is forced to start on DFS channel with BW 160 Mhz
irrespective of BW on which STA is connected without CAC.
Even after STA disconnects, SAP remains on DFS channel with BW 160Mhz.
So, scan will be disabled and STA cannot be connected on any channel
other than DFS channel.
If STA is connected on non-DFS channel on 5 GHz and SAP starts, it
will start on non-DFS channel as primary channel with BW 160 Mhz
without CAC. Also, scanning was also allowed when SAP is started with
BW 160 Mhz. This might violate regulatory in case radar comes up while
scanning.
Standalone SAP on DFS channel was not allowed.
To fix this, Force set SCC for non-dbs HW, this way standalone SAP
can come on DFS channel but scan will be disabled in such case and
STA cannot be connected other than DFS channel.
In case STA gets connected to dfs channel in non-dbs HW, then sap
starts only on STA channel with force SCC with BW
MIN(sta_chan_width, CH_WIDTH_80MHZ).
Afterwards, if STA disconnects, restart the AP with BW CH_WIDTH_80MHZ
on safe channel. Scan will be allowed as the DFS master capability is
offloaded to AP with which STA is connected on DFS channel.
Also, if standalone sap starts, then STA connects to DFS channel then
SAP will restart with STA channel frequency and Channel width
MIN(sta_chan_width, 80MHZ).
If standalone SAP starts and then STA connects to non-dfs AP or SAP
starts when STA is already connected to non-DFS AP, then ch_width is
MAX(sta_chan_width, 80MHZ) (5 Ghz) or 20 Mhz (2.4 Ghz).
If STA disconnects during SAP+STA on non-DFS, SAP won't restart unless
the STA was connected on BW 160 Mhz.
Change-Id: I1cebfc79f170c1e4e2710ed747ec804df3d8b441
CRs-Fixed: 2809255
User reads policy manager connection status information via sysfs
entry. Host adds HW mode dbs capability information in pm_cinfo
by checking HW is dbs capable and present HW state is DBS.
Change-Id: I00d83b49dfae41b17341d3758d8ead42ffd602a8
CRs-Fixed: 2795010
When dcs triggers acs in STA+SAP mode, dcs detection will be disabled
and acs process will be ignored, but dcs detection won't be restored
again when STA disconnects, it's an issue. Dcs detection and acs
process should work normally when STA disconnects.
Fix is to restore dcs detection when ignore acs in STA+SAP scc mode.
Change-Id: I701fd2eec1d6e293c7c5da460a4e5b13d16c0929
CRs-Fixed: 2784177
Add an INI to configure the wow-mode logging config.
So that,the fw would use this bitmap for logging when it
is in wow mode.
Change-Id: Ib2fbd0c5c9cc573b2f5b12dcdf06682c16550cb2
CRs-Fixed: 2810372
Rename struct wlan_cm_connect_rsp to wlan_cm_connect_resp for
better readability and to avoid duplication of the structure
and function name as there is already a function with the same
name.
Change-Id: I331365058ed25b902aae11f979512b4edcd3ac06
CRs-Fixed: 2809137
Macro ROAM_OFFLOAD_V1 is useless since new rso path code is
used, clean up all ROAM_OFFLOAD_V1 related code.
Change-Id: I0f6f2171a62b5c0cfb5333104be7eabc705dfef8
CRs-Fixed: 2812277
