Currently some channel list modifications for SAP and P2P GO mode
are present in policy_mgr_get_channel_list, whereas separate APIs for
SAP and P2P GO specific channel list modification are present, hence
keep all the mode specific channel list modifications in respective
APIs.
Change-Id: I393fbad12f29c761c1158fc5eb4ba0ebd6a660b6
CRs-Fixed: 3321108
When g_sta_sap_scc_on_lte_coex_chan = 1, SAP is allowed SCC with
STA on unsafe channel.
Use API policy_mgr_is_sap_freq_allowed to check such condition
in wlansap_get_chan_band_restrict.
Change-Id: I62b3ad83ccdfc80b5e72cad733618326e4fed936
CRs-Fixed: 3368195
The kernel-doc script identified a multitude of documentation issues
in components/pkt_capture, so fix them.
Change-Id: I9fc7922978cbfacf3f8a733561dd0f94c6cea3b4
CRs-Fixed: 3359684
The kernel-doc script identified a few documentation issues in
components/ocb, so fix them.
Change-Id: I3ddb0c4d556f459bdd15f9ae9110ae7f0bc30b2b
CRs-Fixed: 3359569
The kernel-doc script identified a few documentation issues in
components/p2p, so fix them.
Change-Id: I24e612e8976e721281a6ede4afefd20de0622599
CRs-Fixed: 3359593
The kernel-doc script identified a multitude of documentation issues
in components/nan, so fix them.
Change-Id: Ibec4c381da3088f704264d04f756d82d20613c46
CRs-Fixed: 3359549
The kernel-doc script identified two documentation issues in
components/ftm_time_sync, so fix them.
Change-Id: Iebcd1837bd80e26db6a4a5fe78d046d57f762670
CRs-Fixed: 3357062
The kernel-doc script identified a multitude of documentation issues
in components/fw_offload, so fix them.
Change-Id: I9c5b3f561d74ac433bd7f8c47cab737af9af3ecb
CRs-Fixed: 3357050
In lim_send_assoc_req_mgmt_frame host allocates memory
for ie according to the add_ie_len, add a check
to verify if add_ie_len is non-zero before
API calls where add_ie is sent and used without
being verified.
Change-Id: I8856bb79ac15aeaf643ae8414ea6799aac199feb
CRs-Fixed: 3351656
For legacy STA like wlan1, has no MLD addr, can't copy it after roaming,
or vdev self MAC becomes 0.
Change-Id: Ia5d1f01d9101bfaba275cc879a14f2b8c6426d3b
CRs-Fixed: 3366012
Currently host sends many vdev/pdev set param commands
to firmware during vdev create/start/peer create from
wma_dev_if.
Combine all vdev/pdev set params of wma_dev_if,
send to WMI to reduce number of transactions.
Also replace target wmi pdev/vdev params with host wmi
pdev/vdev params.
Change-Id: I8dd5a5b85d0458b3c79b8585c08b6e282ee3fd94
CRs-Fixed: 3333613
Currently wma_set_sw_retry_threshold sends two
pdev set param commands separately to firmware
Combine two sw retry threshold pdev set params,
send to WMI to reduce number of transactions.
Also replace target wmi pdev/vdev params with host wmi
pdev/vdev params to fix existing broken layering
violation.
Change-Id: Ia66a3e8e50002691008f66253d8cd76d2a1e9aa8
CRs-Fixed: 3333454
Currently host sends bmiss set param commands
separately to firmware.
Combine bmiss set params send to WMI to reduce
number of transactions.
Also replace target wmi vdev params with host wmi
vdev params to fix existing broken layering
violation.
Change-Id: I5867ee76f68abf462becafc1f5f80c422c239f4b
CRs-Fixed: 3333237
Currently wlan_mlme_configure_chain_mask API sends many
pdev set param commands separately to firmware.
Combine all pdev set params of wlan_mlme_configure_chain_mask
send to WMI to reduce number of transactions.
Also replace target wmi pdev params with host wmi
pdev params to fix existing broken layering
violation.
Change-Id: If0b7bce9a7c87d0f07e7a9f1d2cd80139f027308
CRs-Fixed: 3151438
Currently in wma_extscan_hotlist_match_event_handler
API, dest_hotlist get memory allocation based on numap
which takes value from event->total_entries.
But numap is limited to WMA_EXTSCAN_MAX_HOTLIST_ENTRIES
and event->total_entries more than WMA_EXTSCAN_MAX_HOTLIST_ENTRIES
can cause out of bound issue.
Fix is to populate dest_hotlist->numOfAps from numap
instead of event->total_entries to avoid any out of bound issue.
Change-Id: I756f7e4a4dcd454508bba83d4a8bbbb139530905
CRs-Fixed: 3346781
When update rate info to vdev mlme_priv, if in current assocrsp
there is no extend rate or mcs rate, need to clear such info.
otherwise such info is still last connection information.
the link rate will display wrongly, test step as:
1 connect with 11g AP
2 config AP to 11b, then connect manually
3 link speed will be wrong on sta side
if extend rate or mcs rate is not present, clear ext_opr_rate_set
and mcs_rate_set.
Change-Id: I8ff1b5804dbbe463d6949d0431079174446c64ad
CRs-Fixed: 3356077
XGAP power save event need host actions and notifying
the userspace.
Register for XGAP events to wake up host.
Change-Id: Ic58837580a35bd27ac5e87fc5debbd4f4d5b9b6b
CRs-Fixed: 3272421
Currently host uses nla_put_u32 for time_slice_duty_cycle
but it's an uint8 variable.
In order to address this issue use nla_put_u8.
Change-Id: I55024b0daeaf0219e3fe93ddb43b2da0c69c38e3
CRs-Fixed: 3347871
Currently host driver is indication the ML AP/STA support to the
kernel at once, the kernel is expecting different iftype data
population of ML STA/AP.
Populate the configuration independently for STA/AP.
Change-Id: Icbd422413e1fa92471a37557c77af921dc0e8f10
CRs-Fixed: 3366164
When roaming from legacy AP to MLO AP, during the pe session
creation for the link vdev, the bss descriptor is allocated in
lim_cm_fill_link_session(), but its already allocated as part of
lim_join_req allocation and is not freed.
Don't allocate memory for bss_desc pointer again in
lim_cm_fill_link_session() api.
Change-Id: I1d4e0683df04e8bbf307e595cb5ac5e36ca24586
CRs-Fixed: 3363077
On add virtual interface through cfg80211 ops, the params
to create adapter as ML will set for SAP mode.
However if SAP interface add is called internally in the
driver without setting the params to create the adapter
as ML type then, interface will be created in non-ML type
and ML SAP bringup fails.
Implicitly assume all SAP mode open adapter requests as ML type.
Change-Id: I7d16cfe4f20ec0d55aa520ae031069e4b2bc6869
CRs-Fixed: 3362622
If EAPOL exchange fails for the any ML client connecting to ML SAP,
the deauth frame is sent with MLD address of the respective client.
This can lead to peer look up while preparing deauth frame and will
drop sending deauth frame.
For ML SAP session, if the peer address received is MLD address,
then change the address to primary link's address of the peer.
Change-Id: Ic23cbdfd60672432347e0837b059aea663a9c510
CRs-Fixed: 3357351
In function hdd_nan_sr_concurrency_update, the FOR iteration has
released the vdev ref if is_sr_enabled is false, but it does not
set sta_vdev to NULL. It causes the last sta_vdev ref count release
again and this causes issue of releasing ref count which was not taken.
Change-Id: Ia218073b4ef2508cd78370bb4236790df9b5ee4f
CRs-Fixed: 3363355
The kernel-doc script identified some documentation issues in
components/dp, so fix them.
Change-Id: Ic6297d80cda845287e7a472add244c489afd253b
CRs-Fixed: 3362039
When STA roams to an MLO AP, non-assoc link might be superior
in features compared to assoc link and the per-STA profile
info may carry corresponding IEs. These IEs are extracted
and added to IE list of link probe response while generating
it. So, the link probe response generated from assoc link
probe response might be of more size than assoc link probe
rsp. Allocate buffer for the scan entry to be added to scan db
and bss descriptor to accommodate all of the IEs got generated
as part of link probe rsp generation.
Allocate MAX_MGMT_MPDU_LEN bytes for IEs as the max frame size
that can be received from AP is MAX_MGMT_MPDU_LEN bytes.
Same is applicable for link scan entry addition to scan db in
case of initial connection.
Change-Id: I2c2bb79176984a98034c071389c60ee4f649fd74
CRs-Fixed: 3359087
Older versions of kernel (<5.12) support the interface creation
through vendor command. But newer versions of kernel(>5.12) expect
the NDI interface creation to happen in two phases due to RTNL lock
removal for the vendor commands.
1. Create an interface through add_virtual_intf in STA mode
2. Change the mode to NDI through vendor command.
Currently, host driver restricts NDI creation to MAX_NDI_ADAPTERS(2) in
kernel versions < 5.12 and same is applicable for newer kernels as well.
Add the same check in NDI start for kernel versions >= 5.12.
Currently, host driver uses macro "MAX_NDI_ADAPTERS" to limit the NDIs.
Use the value of ini param "ndi_max_support" instead as this can be
configured differently(1 or 2) for different targets.
Change-Id: I355c42d60d6b86b4664ed001d7ed4d163a102159
CRs-Fixed: 3362601
