As part of protected dynamic interface control feature,
if WiFi is disabled by user space, WLAN HW is also disabled.
If the device gets rebooted, then user space might not know
the current WLAN state. Add logic so that, user space can
always know the current WLAN state.
Change-Id: I00c913dbaec2031c7b3505fafd11471087a2c623
CRs-Fixed: 3225969
WLAN HW can be disabled at boot and thus wlan boot activities will be
deferred. Add PLD API to start wlan boot time sequence in platform
driver after HW is enabled.
Change-Id: I9dcdc9944b7f71dc3488a20719ca36c00ae62a4e
CRs-Fixed: 3222032
Currently host sends first, final bmiss count to fw
Add support for bmiss timeout(in seconds)
during wakeup as well as sleep state to fw.
Change-Id: Id748fabdff94f5fa3038bcea1b1cac733ac2dbe1
CRs-Fixed: 3224106
Add vendor handoff service bit capability support
WLAN_SOC_VENDOR_HANDOFF_CONTROL to check whether the FW
supports vendor handoff feature or not.
Change-Id: Ifdf541761716df9ca5b764c05714a8b501642354
CRs-Fixed: 3224573
Make changes in packet logging to send QDF status
and type instead of packet log type and status.
Change-Id: I8c1d04a78272159f7d34d6034c41d52e1e44b61d
CRs-Fixed: 3224876
Add new flag CONNECTIVITY_PKTLOG to make independent of
FEATURE_PKTLOG and REMOVE_PKT_LOG for packet logging.
This is because 32 tx/rx pkt logging is connection related
and this feature is independent of pkt log feature. Here
driver will send first 32 tx/rx pkts consisting of mgmt
and data pkts to userspace which can be used for debugging
Change-Id: If987ac8b6cb10b464a4ec2ace1c55215c0aa3614
CRs-Fixed: 3222970
Move change Ic8dfdb09c73a1071678612430fff2f23180ad336
Use skb_orphan instead of skb_unshare in TX to DP component
Change-Id: I0372a5c58f96a40d81a6670f507870dbfac63170
CRs-Fixed: 3226184
If primary channel is punctured, set assoc_cnf.resultCode as
eSIR_SME_INVALID_ASSOC_RSP_RXED, set assoc_cnf.protStatusCode as
STATUS_UNSPECIFIED_FAILURE and send disassoc frame.
Otherwise sme layer still considers it as a valid connection.
Change-Id: Ia36ddfba66febd4c9ddcc5e06cd6acd5f27a93bb
CRs-Fixed: 3224968
The API wlan_get_operation_chan_freq will return 0 if
vdev is starting, which is unexpected.
Fix by remove vdev "active" check for get operation chan API.
Change-Id: I12999a68aa74da931ed847b0b696ef49325daa1d
CRs-Fixed: 3225525
Currently PM_STA_SAP_24_STA_5_DBS is not added in fourth connection
pcl table, due to which pcl is becoming 0 in case of P2P on 2 GHZ doing
MCC/SCC with one STA 2 GHZ link and one STA link on 5 GHZ in DBS.
Fix is to make PM_STA_SAP_24_STA_5_DBS same as PM_24_SCC_MCC_PLUS_5_DBS,
so that next/fourth connection can come up on PM_SCC_ON_5_CH_5G.
Change-Id: I4b4c346a998c24ab090307982f1ef6da90bb507c
CRs-Fixed: 3225380
In the current driver implementation, the vdev_id sent by FW
is ignored by link stats peer and radio event handler. It leads
to vdev_id mismatch in wlan_hdd_send_ll_stats_req and ultimately
causes LL_STATS timeout. To void this issue, update correct vdev_id
sent by FW in the link stats peer and radio event handler.
Change-Id: I283f8a8f4f4d4b3018072ecc0f19d55cf47d03eb
CRs-Fixed: 3224704
For FT-FILS AKM, 1st connection to an AP in a realm takes place
with Full EAP. 2nd connection to any AP in the realm does the
FT initial mobility domain association with authentication
algorithm as FILS. Subsequent connection/roam happens with
FT protocol.
fils_ft key is derived during 2nd connection. But driver
copies from fils_ft buffer after 1st connection is complete
to fill the PMK in the 11r TLV. This causes the pmk len = 0
is sent in the 11r TLV.
Fill the initial connection PMK in RSO command after 1st
connection. From 2nd connection onwards fill the fils_ft.
Change-Id: I52399fc7bd3526a11e29c54a3ca13d43bbaf6b80
CRs-Fixed: 3197226
Currently, Host starts a 1-sec timer (WLAN_WAIT_WLM_LATENCY_LEVEL) and
sends WMI_WLM_CONFIG_CMDID to FW for non-STA device mode also. But
FW replies back with WMI_VDEV_LATENCY_LEVEL_EVENTID to report latency
level honored by FW only if HOST sends WMI_WLM_CONFIG_CMDID for STA
mode.
If host sends WMI_WLM_CONFIG_CMDID to FW for non-STA device mode,
host always observes WLAN_WAIT_WLM_LATENCY_LEVEL timeout.
Fix is to allow host to send WMI_WLM_CONFIG_CMDID to FW only if
adapter device mode is STA.
Change-Id: I3d9f588611eff0493ba3fffd05666da64c7f5da2
CRs-Fixed: 3221831
Add support for new ini param RoamScan_InactiveTimer. This param
is similar to the existing roam_scan_period_after_inactivity but
unit change
Change-Id: I0e803decaba30fa3f2dfcd95dc62dc71aa1cb3cd
CRs-Fixed: 3016893
GETROAMSCANCONTROL and SETROAMSCANCONTROL driver commands
will be deprecated from Android 13. So remove all logic
related to these driver commands in the host.
Change-Id: I05fafbec2b3f3b798c8c89d0c33b1dbf5c1b45d4
CRs-Fixed: 3225052
Add cfg item to enable/disable eMLSR mode for ML STA
under 802.11be op mode. The cfg value 0 corresponds
to default MLMR mode, 1 corresponds to eMLSR mode.
Change-Id: Ib02516aac8ac44aee6b40a572a9f7469b10d0ac2
CRs-Fixed: 3184745
Add support for new ini param RoamCU_MonitorTime. This param
is similar to the existing bss_load_sample_time but unit
change
Change-Id: Iae05a9568aa29a5f6a9cfc771e66184e51963ab6
CRs-Fixed: 3015967
With restructuring in hif runtime pm module, modules are
required to register with the hif runtime pm module. Also,
link states are depreciated.
This change registers PM QOS and bus suspend modules which
use runtime PM module and replace link state with resuming
link up state in PMO resume.
Change-Id: I0df48e3d31a1fb0f03faaa0617b48937c9bc224b
CRs-Fixed: 3169425
To support shutdown WLAN when system goes into suspend, add idle shutdown
when got PM_SUSPEND_PREPARE/PM_HIBERNATION_PREPARE.
Before suspend/shutdown, user space should stop adapter. And after resume,
user space should restart adapter. This can ensure user and kernel space
to sync adapter's state.
Change-Id: Id1f5172a7fc1792c83c8c1c20127de815f7e4980
CRs-Fixed: 3208931
When MLO SAP is started with two different bands, the 2.4 GHz
link follows the 5GHz and restarts on the same channel
as 5 GHz link.
The user configured frequency for the SAP is cached on the
psoc, therefore during the concurrency check after bringing
up the second connection, 2.4 GHz link considers the new
user configured frequency of 5GHz link and moves to the same
channel.
Save the user configured frequency per vdev to prevent
cross-utilization.
Change-Id: I62f883bf818332bb7d0c838e6ed629a8f2d2f21b
CRs-Fixed: 3209394
-Wimplicit-fallthrough is being enabled by default. Some compilers
such as clang require the attribute instead of just a fallthrough comment.
Change-Id: If55d68cb76589b39b88d859ea4d9fa6e10246c7e
CRs-Fixed: 3217399
-Wimplicit-fallthrough is being enabled by default. Some compilers
such as clang require the attribute instead of just a fallthrough comment.
Change-Id: I7a04c8727121f58a5d6dcd575446c9acedea164b
CRs-Fixed: 3216248
Currently, vdev in link set active request is added
without any check whether it is ml sta vdev or not
due to which may cause issue of empty event for that
particular vdev when sap/p2p vdev is added instead of
ml sta vdev in request.
Fix is to add ml sta vdev in link set request to avoid
mismatch with fw link down and expected vdev down from
host to avoid empty event failure
Change-Id: If99b305c267f094913b8d9ce96a330eed47d0214
CRs-Fixed: 3221818
