FW may experience HWDTIM mode enter and exit, if HOST can't queue
frames fast enough, this will bring 10ms latency for TX under WoW.
This change adds an indication bit to notify FW whether a TX happens
after WoW wakeup, then FW can discard HWDITM and reduce TX latency.
Change-Id: I74f7311fc0639186ee0bca711160bb8c0d5d9fb3
CRs-Fixed: 3055501
The ini gEnableWoW was designed to enable or disable both magic
pattern match and pattern byte match, but now host ignore the
magic pattern setting from the ini, always enable the magic
pattern instead.
configure magic pattern in line with ini gEnableWoW setting.
Change-Id: I309aff03de9bdbd36fe391784ba54cbfa0cad67b
CRs-Fixed: 3047199
When connect with assoc_ie has HS20_OUI_TYPE ie, hs_20_ap should
be set to true for using afterwards.
Change-Id: Id3003290473bdfa0adb0fc6471ae052e7944ab3d
CRs-Fixed: 3056979
Max supported bandwidth and 160mhz short GI is advertised max
supported by the device. This could cause conflict at STA side
due to difference in current operating bandwidth and capabilities
advertised in VHT capability IE.
Configure VHT capabilities based on the operating bandwidth.
Change-Id: Ia548ed0b39284f5624920800075bc614872c1595
CRs-Fixed: 3052687
For deauth/disassassociation RX/TX, the connectivity logging event
is sent. In this event the QCA_WLAN_VENDOR_ATTR_DIAG_STATUS_CODE,
is used to send the frame reason code. But userspace expects
QCA_WLAN_VENDOR_ATTR_DIAG_REASON_CODE attribute.
Fill QCA_WLAN_VENDOR_ATTR_DIAG_REASON_CODE instead of
QCA_WLAN_VENDOR_ATTR_DIAG_STATUS_CODE.
Change-Id: I90d58f251f0e2d4647cbde3c76d4a22779c97290
CRs-Fixed: 3054797
Add the changes corresponding to the proto-type changes
for txrx_vdev_atfach and txrx_peer_attach for ol targets.
Change-Id: Ibf31e3d5dd7cdf8c47ab3fe9cfdcbfd5762dc18d
CRs-Fixed: 3053683
As DP requirement, CP should not provide peer mlo information for
cdp_peer_create and CP should provide peer mlo information for
cdp_peer_setup.
Change-Id: Ic15f209b009e5a3bd6b154992d2a88cb19f489de
CRs-Fixed: 3020662
At present lim_is_medium_time_valid returns failure for
reassoc case since it only checks pe_session->lim_join_req.
To resolve this issue, checks pe_session->pLimReAssocReq too.
Change-Id: I78ab6e548c590cb16dc71a16e861ecc940601b96
CRs-Fixed: 3056363
In delete pmksa call for FILS case, the userspace sends only the
ssid and cache id on the pmk cache. But the driver copies only the
bssid which could cause invalid bssid being copied and the delete
pmksa operation fails always.
Fill pmksa ssid if SSID and cache id are provided, else copy the
bssid. Also add additional debugs for FILS RSN IE.
Change-Id: I7836156e0fe4c885d35fd8791dfe3bf958a88522
CRs-Fixed: 3036327
Enable CONFIG_HAL_DEBUG if CONFIG_SLUB_DEBUG_ON is Y
to fix the compile issue for HST.
Change-Id: I1fd8760f543f6d739af994b8b4b4ca3684dd3686
CRs-Fixed: 3054445
For SBS Frequency range, the frequency range can
be of Either Lower 5Ghz Frequency shared with
2.4Ghz Frequency or Upper 5Ghz Frequency shared
with 2.4ghz phy.
Add support for both the shares.
Change-Id: Ibf17cf155e52534e029bd596f70349faf8cc03ee
CRs-Fixed: 3056464
As part of stop modules, the deinit connectivity logging happens and
the queue, all the pointers are deinitialized. But while
initializing the write pointer the write pointer spinlock is not
acquired. This results in null pointer dereference of write_ptr
from other context.
Protect the access to the write pointer before setting it to
NULL in wlan_connectivity_logging_stop().
Change-Id: I69dc57b9e661004203f58754824496953105726f
CRs-Fixed: 3054306
Since the code under FEATURE_HAL_DELAYED_REG_WRITE_V2 has been
removed and cleaned up, removing the build flag from Kbuild.
Change-Id: I66072af952877881fb700869ae4774e4f1a388cc
CRs-Fixed: 3056477
In if_mgr_validate_candidate() adds SBS
check to allow a STA connection on SBS
channel when MCC is not allowed .
Change-Id: Ia8007a4beabf546ff293986124f4ef985ccaeacc
CRs-Fixed: 3052797
The spin lock pm_qos_lock is used in disconnect handler,
but it maybe not initialized if run time pm not enabled.
This will cause spin lock bad magic check failure issue.
Fix it to create spin lock during pm qos notifier register.
spinlock bad magic on CPU#7, kworker/7:2/691
lock : 0xffffff815bf93170, .magic: 00000000,
.owner: <none>/-1, .owner_cpu: 0
------------[ cut here ]------------
Internal error: Oops at kernel/locking/spinlock_debug.c:73!
Call trace:
spin_dump+0x7c/0x80
do_raw_spin_lock+0xbc/0x124
_raw_spin_lock_irqsave+0x38/0x4c
hdd_cm_disconnect_complete+0x14c/0x2e4 [wlan]
osif_cm_disconnect_comp_ind+0x38/0x8c [wlan]
osif_disconnect_handler+0x200/0x228 [wlan]
osif_cm_disconnect_complete_cb+0x10/0x1c [wlan]
mlme_cm_osif_disconnect_complete+0x40/0x84 [wlan]
cm_notify_disconnect_complete+0x34/0xec [wlan]
cm_disconnect_complete+0x3c/0xdc [wlan]
cm_send_disconnect_resp+0x64/0x90 [wlan]
cm_state_init_event+0xc8/0xe4 [wlan]
wlan_sm_dispatch+0x168/0x1e8 [wlan]
cm_sm_deliver_event+0x11c/0x1b8 [wlan]
Change-Id: Id78e1e13ceded7cfefc40a8a86f74fe976b9aa75
CRs-Fixed: 3055380
Currently during wlan suspend DP refill thread is suspended first
then RX thread is suspended but if RX thread suspend fails then
refill thread should be resumed if not refill thread will be stuck
in suspend state forever.
To avoid refill thread getting stuck in suspend state, resume
refill thread when RX thread suspend failure is encountered.
Change-Id: I2dfdfa881bb3cb660b83067c796d3a833b86ef5f
CRs-Fixed: 3054903
In SAP+STA DBS case, STA twt session gets teardown when SAP
becomes active. This is because ext_conf_present is set as false
in both req/res disable api due to which
TWT_EN_DIS_FLAGS_SET_SPLIT_CONFIG, TWT_EN_DIS_FLAGS_SET_REQ_RESP,
and TWT_EN_DIS_FLAGS_SET_I_B_TWT becomes 0 and sends disable cmd
for both req/res in firmware.
As part of fix, set twt ext_conf_present as true so that disable
cmd will be send based on role.
Change-Id: I64c8c30af3eef22c75e29de5f674630d091fda04
CRs-Fixed: 3048284
Roam result is printed as failure always since the
is_roam_successful flag is not passed to the
roam successful attribute to userspace. For roam
reason, the wrong attribute is used to convert the roam
sub reason from driver values to userspace values.
In WTC roam, the sub reason & vsie is not filled
from the right roam trigger TLV.
Fix the connectivity logging roam result and roam
subreason and WTC values passed to userspace.
Change-Id: Id276054868d907a801e87c1fd9cd7bb3b7c4e150
CRs-Fixed: 3051447
Currently, WOW wake up event is logging the critical messages
using the fatal log level. These logs are not fatal but critical
to know the reason of the WOW wakeup.
Change the WOW critical log level from fatal to info.
CRs-Fixed: 3052107
Change-Id: Iebd1e08ca5d75eb5b312fa19820702b514dd03f9
DP_RX_THREAD_WAIT_TIMEOUT is defined in one macro but
derefereced under another macro. Change is to align
the macro in-use.
Change-Id: I839b2b024c2b2301a585b6ca8016ac64fb3899f2
CRs-Fixed: 3055419
In function wlan_cfg80211_tdls_extract_6ghz_params(), the length of
req_info->he_6ghz_cap is two bytes, but with a copy length of the
length of pointer params->he_6ghz_capa. Make sure the righ copy
length is used here to avoid OOB.
Change-Id: I8e98c2a72ab032c3da9e0e213d1ea85f0653e0cb
CRs-Fixed: 3047149
For SDW5100 release branch path for common dir is changed to
device/qcom/common/monaco which is being specified in target mk file.
This change ensures other SI compilation will not break.
Change-Id: If8aa35a2e2da0e42b34c77ff8097c26aa2aa83d1
CRs-Fixed: 3020014
For STAUT to follow the rules governing OBSS Narrow Bandwidth RU in
UL OFDMA Tolerance Support, bss_color_collision_det_sta to be set
to 1.
Change-Id: Ibe283f8bec9febbaf9a876d1afd55389ea4c971d
CRs-Fixed: 3053624
This logic belongs in connection manager so remove it from HDD.
This reverts change I7eca69b8a0b0f7018326681be14197b3482e859d.
Change-Id: Ie58f4a988c7118eeda02762a2e2965c21596cd8f
CRs-fixed: 3054186
