The functions sme_send_he_om_ctrl_bw_update() and
sme_send_he_om_ctrl_nss_update() were removed by the following patch:
qcacld-3.0: Add support to configure HE +HTC support and OMI Tx
Change-Id Ic3ad5952198472ecda79471a37ff527dfdbcdbf0
However the prototypes were not removed, so remove them now.
Change-Id: I8d3bc19b629d22eb06161dff972388d816b652ab
CRs-Fixed: 3424786
wlan_mlme_public_struct.h has some documentation that is not being
processed by kernel-doc since it isn't using the kernel-doc comment
indicator "/**". Fix those comments, and also fix the documentation
syntax errors now reported by kernel-doc.
Change-Id: I407b5abefe8313071e5e99d52d69f181880c431d
CRs-Fixed: 3424372
enum pkt_origin is unused, and is poorly defined so it should not be
used in the future, so remove it.
Change-Id: Ia51ffa4518b36ea50f9ed67007978e228b18c7fc
CRs-Fixed: 3424371
For QCA_LL_LEGACY_TX_FLOW_CONTROL data flow control,
currently it cannot support TX off for thermal mgmt.
Similar to thermal implementation in FW, refine
ol_tx_set_throttle_phase_time() to support thermal
mitigation TX off processing when INI throttle duty
cycle set to maximum 100.
Change-Id: I208288bda2ad7ca1a14be0b80a0d57361ce0ec8c
CRs-Fixed: 3413545
The following change removed most of the legacy crypto code following
the transition to the converged crypto component:
qcacld-3.0: Cleanup CRYPTO_SET_KEY_CONVERGED for WMA layer
Change-Id If70fc5cb01f2a0123030c92410e126ce8078e1c6
This change removed wma_setup_install_key_cmd(), but left behind the
now unused function wma_fill_in_wapi_key_params() that it used to call
when FEATURE_WLAN_WAPI was enabled.
So remove the unused function, along with struct wma_set_key_params
which is now unused as well.
Change-Id: Ie16d6ce20d8f5f99ef1c625b34bea3685d3d8029
CRs-Fixed: 3424774
Function lim_process_rx_channel_status_event() was removed by:
qcacld-3.0: Refactor code to store chan info status in cp_stats
Change-Id I2e7219c112e96916d3b73f974dd9803b9c2821c3
However the prototype was not removed then, so remove it now.
Change-Id: I2c3fa2bd3ae70cb8a16d6dd6a57ec298a6c32423
CRs-Fixed: 3424284
The follow change removed all usage of the t_wma_handle ocb_config_req
member:
qcacld-3.0: Clean up OCB legacy code
Change-Id Ib8a26c9e67e78e53f8b2b4929276060687254ea1
However the member itself was not removed, so remove it now.
Change-Id: Id61a2575b9e7d447bb88133322fae9aa7ef33cb5
CRs-Fixed: 3424783
As part of new requirement of 'SAP PS with TWT enabled',
send configured ini value 'g_sap_ps_with_twt_enable'
through vdev set param i.e whether power save
enabled or disabled, during vdev_create to the firmware.
Change-Id: I22fa5754229b5efd7fe3f9b97e0e565f31c01949
CRs-Fixed: 3421619
As part of new requirement of 'SAP PS with TWT enabled',
add ini 'g_sap_ps_with_twt_enable' support in host
to enabled/disabled SAP power save with TWT enable.
Change-Id: Iea76f9cdef6f0753a6dfcebedc2aeab17d121faf
CRs-Fixed: 3421610
As part of modification
of reg_set_channel_params_for_freq API to
reg_set_channel_params_for_pwrmode to make it
compatible with new API need to modify
the wlan_reg_get_usable_channel with extra argument
of REG_CURRENT_PWR_MODE, to invoke
reg_set_channel_params_for_pwrmode which is having
extra parameter of type supported_6g_pwr_types.
Change-Id: I4589bc604ae6bbe25f24c4d0261bcf96347589a8
CRs-Fixed: 3311839
Add bool flag to mlme_vdev_disconnect_peers legacy callback.
This flag will be used by WIN. MCC should ignore this flag.
Change-Id: I693d1aeda1109a987311c1b87346960bed52309f
CRs-Fixed: 3403218
Vdev ref WLAN_OSIF_STATS_ID leaked in corner case, then vdev was failed to
delete, assert happened.
Change-Id: I20b102804d4c3e89be14d89d261996025750be93
CRs-Fixed: 3423850
Support mld self roam between DBS(2 GHz+5/6 GHz) and HBS(5 GHz+6 GHz).
Change high rssi config.
Change-Id: Icb65f26509848a09fe46bf01154a0f42efa073f2
CRs-Fixed: 3416549
ESE Connection param exist in both mlme_cfg and pe_session.
Current params saved in mlme_cfg can be retrieved from psoc directly.
Support in pe_session is no longer needed. Remove params from
pe_session and update functions to get mlme_cfg flag.
Change-Id: I202f6f5b7003eba64d77e5dd70fdf9a03f01183b
CRs-Fixed: 3415748
When do continuous reassociation test, It's needed to free
session_entry->limAssocResponseData first before assigning
new assoc_rsp, otherwise all previous allocated assoc_rsp
don't have chances to be freed except the last reassocation,
and memory leak will be detected.
Change-Id: Icf9056369b5f1d390b1393d5942cefe116d03417
CRs-Fixed: 3419762
3-link ML connection/roaming expects link id to generate link
specific (re)assoc response from received (re)assoc response.
This info is fetched from pe_session but it's not populated
properly in case of roaming. Roam sync indication carries all
links info whereas the assoc rsp generation API expects the
link info for which it has to be generated.
Copy partner link info only from roam sync indication to
pe_session to cater the same.
Change-Id: I75c9a42688f7613ca3f1afab8afe77622bb659aa
CRs-Fixed: 3412939
Code analysis identified dead code protected with the obsolete feature
flag ANI_SIR_IBSS_PEER_CACHING, so remove all logic associated with
that flag.
This is cleanup from a previous patch:
qcacld-3.0: Cleanup IBSS code from LIM
(Change-Id Idebb0f55aa27751f1fdd7b4c1fb8124ae29eb382)
Change-Id: I67a6b2b4747a774b5e116f017b7ef1be0fc5b2f7
CRs-Fixed: 3423129
Currently if host driver requests for idle shutdown and SSR is
in progress then platform driver waits for the SSR to complete and
then call the idle shutdown callback to the driver.
But as a part of SSR shutdown sequence, driver flush this idle shutdown
work and this leads to the deadlock.
To resolve this issue, below changes are required.
1) Platform driver rejects the idle shutdown request with -EBUSY
if SSR is in progress.
2) Host driver runs this idle shutdown work after the reinit if all
the interfaces are down.
3) Remove the work flush from shutdown sequence.
Change-Id: Icae043971715948280dbafc4023fd58bdc1cc564
CRs-Fixed: 3421819
STA DUT sends RSNXE IE with PASN related capabilities by
default based on the target capability. But, connection
failure happens with some APs if the PASN capabilities are
set in the RSNXE IE.
Therefore, update the RSNXE stripping logic as follows:
For WPA3 connection where the AP doesn't broadcast RSNXE IE,
strip all capabilities other than WPA3 capabilities(SAE_H2E
and SAE_PK).
Change-Id: Ifba2894054635962dcb923e4d98418ad1d3ffc7f
CRs-Fixed: 3415097
The last usage of enum hdd_auth_key_mgmt was removed with the patch:
Change-Id I2934e4a867458561c50170b0e786e63f20f1af4a
qcacld-3.0: Code cleanup for connection manager in HDD
Since this is unused, remove it.
Change-Id: I96a2f82e229ca73061da3ed781518d43c940cfa7
CRs-Fixed: 3422049
Issue: Host reports different RSSI values during roaming
trigger logging and subsequent deauth TX logging to user
space.
In case of roam trigger roaming, driver sends the rssi value
to user space from wmi_roam_ap_info tlv in roam scan results.
In case of disconnection due to BMISS or STA KICKOUT case,
host does not receive latest beacon from FW. This results,
on disconnection, host reports deauth TX logs to userspace
using old RSSI present in mac->lim.bss_rssi which is updated
when beacon or probe response is received in host.
Fix is to update mac->lim.bss_rssi while processing sta
kickout or bmiss event coming from FW.
Change-Id: I108f94959fbf915d8f67f443a9fcd54d595c27d1
CRs-Fixed: 3417363
Firmware sends beacon/probe rsp received to host as part of roam
sync(frame) indication. Frame received frequency is same as
re-association frequency in case of non-ML or single link ML
roaming.
But the ML probe response might come from non-assoc link in case
of multi link roaming. Probe response received frequency and
reassociation frequency are different in such cases. Some
IEs(e.g. HT_INFO) expect frame received frequency to match with
the frequency mentioned in the IE.
So, fetch the probe response received frequency from source
address of the frame and the ml_info of roam sync indication.
Change-Id: Ife96aa46de10d4cd6882e6d04479dfdd481582d4
CRs-Fixed: 3412842
The header file pktlog.h is a legacy remnant that doesn't provide any
value, so remove the unnecessary #include. This is a precursor to
removing the actual file.
Change-Id: Ic9def32b2c800a9b05001eb3816d1b421f82288e
CRs-Fixed: 3420816
EasyMesh controller need backhaul station TX rate to calculate path
capacity in EasyMesh steering.
Run time TX rate is more suitable for EasyMesh controller to select
best path.
Backhaul station should indicate run time TX rate to EasyMesh
Change-Id: I2e72257327682235351bc04edf405f73b663a9f7
CRs-Fixed: 3420875
Given the fact that the RX nbuf history array size is not enough,
sometimes the dump fails to capture the problematic buffer address
records, leading to failing to identify sources of buffers. This
change is to increase the array size of qdf_nbuf_history, which
makes it possible to record more RX history buffers to be traced.
Change-Id: I7982873daf6fafcb31e77d2aec380f1c00401ee5
CRs-Fixed: 3405585
In MLO STA 2.4 GHz + 5 GHz High band and SAP concurrency case,
5 GHz Low band SAP will move to MLO 5 GHz link's home channel for
SCC after MLO STA is up.
But GO starts on 5 GHz high band when SAP CSA is in process and
pass the policy mgr concurrency check because the SAP channel
is still 5 GHz low band.
Fix by defer GO BSS start if any CSA is in progress and also
check any AP start is pending for STA, SAP force SCC concurrency
handling.
Change-Id: I0fcd799017d5048f3574687f913a396ab4d7ade1
CRs-Fixed: 3418351
Currently thermal level can be got from upper layer only
for FW thermal mgmt offload case. Per the requirement,
refine the code to support it for thermal non-offload
case as well.
Similar to offload thermal mitigation, add TX_OFF and
shutdown two states for non-offload case. Host will fully
stop TX traffic in TX_OFF state and target will trigger
shutdown when temperature come to the range of shutdown.
Per above requirement, add below four INI to configure
thermal temperature threshold value as need for TX off
and target shutdown.
gThermalTempMinLevel4
gThermalTempMaxLevel4
gThermalTempMinLevel5
gThermalTempMaxLevel5
Change-Id: I40d097ab8a5801052553ad7adedd38be475c7669
CRs-Fixed: 3413165
The current way in the driver to handle CONFIG_CNSS_UTILS=m and
CONFIG_WCNSS_MEM_PRE_ALLOC=m will not work if the flags are not
coming from kernel Kconfig directly (e.g. CNSS utils and prealloc
module sources are built out of kernel tree) since "cppflags-
$(CONFIG_FLAG) += -DCONFIG_FLAG" will not take effect if CONFIG_FLAG=m.
Fix it in a proper way to work even if config is defined as m.
Change-Id: I60c26b1e0d64277b733e534960a00afb5579fb43
CRs-Fixed: 3419566
Do not pass mode as an argument in policy_mgr_is_vdev_ll_sap().
Use vde_id to get the mode for further condition check.
Change-Id: Ie12c31d4cf536ba6c80f0e28524b4c99c23600d1
CRs-Fixed: 3414277
The reference taken for objmgr peer during ML peer
context creation is not released if any validation
has failed in pe_session initialization. The call
to directly remove objmgr is initiated without a
call to detach ML peer. This leads to reference
leak for the peer.
If lim_fill_session_params() API returns error,
wma_remove_bss_peer_before_join() API is called
to cleanup the peer objmgr. Call API corresponding
to MLO peer detach in this function to release
the MLO_MGR reference.
Change-Id: I010150b4aefe9f076455cd5aafb1c3b55155458b
CRs-Fixed: 3405762
