Currently gStaKeepAliveMethod and station_keepalive_method are not
mapped properly due to an offset of one. Fix this by updating enum
definition.
Change-Id: I572ee472b0b45816bf26830060d2b0707c90f387
CRs-Fixed: 3385907
A 802.11be MLD device can have one of the links
address same as MLD address. On add peer for this
MLD peer the validation for existing peers with same
MAC address may fail as a match with existing peer
will be found.
If an existing peer with new peer's MLD address
is found, then allow new peer if both existing peer
and new peer are in same ML dev context, if both
are on different ML dev context, reject the peer
add request.
Change-Id: I30c53032f228f166a1011b330ca245581dfe468b
CRs-Fixed: 3381720
There are quite a few documentation issues in core/pld:
- Documentation of implementations instead of interfaces
- Duplicate documentation
- Syntatically incorrect kernel-doc
Fix all of these issues.
Change-Id: Ia6ef2fda239e9021c879bc4672c9e80ec5c93921
CRs-Fixed: 3386837
Some legacy STA doesn't recognize the EXT CAP IE with
length greater than 8bytes. Therefore, these STA cannot
associate with hotspot broadcasting newer capabilities
in the extended IE.
To fix this, add an ini which would override the beacon
protection config in host driver.
Based on this ini, the beacon protection would be disabled
only for non-6 GHz and non-11be SAP profiles, as beacon
protection is mandatory in 6 GHz and 11be cases.
Change-Id: I672b707f6955fa31938aebba5e25461dd40cee4e
CRs-Fixed: 3378974
There are quite a few documentation issues in core/cds:
- Documentation using legacy Doxygen format instead of kernel-doc format
- Documentation of implementations instead of interfaces
- Duplicate documentation
- Syntactically incorrect kernel-doc
Fix all of these issues.
Change-Id: I7ffdea9027278c75975a826466da2d7204a25d0c
CRs-Fixed: 3386190
In case of 1x MLO roaming, 4 way handshake is offloaded to supplicant
and link vdev is down in FW. Host has to bring up link vdev post
set key installation.
Add handling in host for following:
- During roam sync indication handle only assoc link.
- Save reassoc response and link information.
- After keys are installed bring up link vdev by
queueing connect req on link vdev.
- Enable roaming after all links are up.
Change-Id: I9c0722f88e950ba05ec3dd7f44883bedf568f97d
CRs-Fixed: 3287316
Currently, driver finds PASN peer from BSSID in mgmt auth frame
and with help of this peer, it extracts the vdev_id. It uses this
vdev_id to retrieve the adapter in hdd.
But for NAN iface, there is no PASN peer and driver drops the
auth mgmt frame as no valid vdev_id available.
The NAN Cluster ID is a MAC address that takes a value from
50-6F-9A-01-00-00 to 50-6F-9A-01-FF-FF and is carried in the A3
field of some of the NAN frames.
So, to fix this, compare the first four bytes BSSID with
"50-6F-9A-01" and extract the vdev from vdev_list for NAN opmode.
Change-Id: Ie4f15549e3bd8378e362538da4d7ec49e84ad138
CRs-Fixed: 3382962
Remove passive/dfs acs channel which are configured through
userspace for LL SAP.
Change-Id: If5d3abe920b93af6cb9be02344618e484c3b0778
CRs-Fixed: 3370658
The kernel-doc script identified some documentation errors in the
core/bmi folder, so fix them.
Change-Id: I1ec447b56eb38358c4d875d9e0f1ecbe935be57e
CRs-Fixed: 3385916
In hdd_get_station_info skb buffer gets allocated an
arbitrary large size.
To address this issue, allocate skb buffer size based
upon the destination attribute sizes.
Change-Id: Ie36b0bb67562e302a3abe6d60d0e323ce172236e
CRs-Fixed: 3363955
As per current implementation, SR(Spatial Reuse) commands are
rejected if STA is not connected or connected to AP that doesn't
support SR which causes issue because SR Enable/Disable command
shouldn't reject if STA is not connected instead of rejection
same configuration should be applied when SR AP connects to STA.
Fix is to not to reject SR command if PD threshold is not provided
along with enable command, so that enable command can be accepted and
applied when AP that supports SR connects to station.
Change-Id: Ie4a973053b79d0d5931bcc2520da42f9aab93089
CRs-Fixed: 3350451
lim_update_rrm_capability is only called in lim_fill_pe_session,
which is for station mode.
If only SAP interface exists, mac_ctx->rrm.rrmPEContext.rrmEnable
will not be set.
Call lim_update_rrm_capability for SAP mode.
Change-Id: Icc5e3a960a372b26943987c377ec292c5cf2eb8c
CRs-Fixed: 3380748
In function hdd_cm_connect_success_pre_user_update, the
variable is_auth_required is true by default. During roaming,
it should acquire wakelock if key installation is pending.
But during initial connection, it does not need to acquire
wakelock for initial connection in this function.
Change-Id: I967e6d97dd9c7a40d111b0040ee53876b7be6192
CRs-Fixed: 3383907
Driver sets the bit mask for supported feature to turn on or
set the feature flag for the requested feature.
Add a log to print the supported features bitmap in the driver.
Change-Id: I1a47697f605a62807a9612b2c5bd04491a67cedc
CRs-Fixed: 3383080
When handle deauth, if req peer mac isn't session bssid, pe session id is
used as vdev id wrongly, then deauth rsp is dropped in CSR, disconnect cmd
isn't removed from serialization queue, assert will happen.
Change-Id: I35c2805ae3ea904b2306b2a210c2284498330c04
CRs-Fixed: 3378250
Currently, CSA on an unsafe channel is not allowed.
Allow CSA even if it's unsafe channel when user tries to set
a fixed channel (i.e. reason = CSA_REASON_USER_INITIATED)
and firmware supports the capability
WMI_COEX_FIX_CHANNEL_CAPABILITIES.
Change-Id: I5ba26faabe05fbf1a79dc92360400ec2c6d71b2d
CRs-Fixed: 3381395
Currently, unsafe channels are avoided when SAP restart happens.
If WMI_COEX_FIX_CHANNEL_CAPABILITIES is advertised by firmware
and if the SAP is started in a fixed channel, don't restart even
if the current operating channel is unsafe.
Change-Id: I5f7d632bcc00a1b5351dad64aca0ce16f1057537
CRs-Fixed: 3381394
Current code does not use the SSR host log collection API.
Fix this by adding SSR host log collection API usage.
Change-Id: I364bd6281e886e8c50dfd6f45f78fb98e822f962
CRs-Fixed: 3339953
During T2LM validation to pick assoc link, only check if
operation mode is station and if t2lm ie is valid.
Change-Id: Id31f83fabd22ae0e434e2720df773f778c7bb448
CRs-Fixed: 3370578
Currently, SAP start is aborted if the channel is marked as unsafe
due to COEX, irrespective of it's an ACS/fixed channel SAP.
There is a requirement to allow the SAP in a fixed channel even
if the channel is marked as unsafe. Firmware advertises
WMI_COEX_FIX_CHANNEL_CAPABILITIES in such targets.
Check for this capability and allow the SAP in fixed channel even
it it's unsafe.
Change-Id: Ie3947058d8854823a718b833ec788c5c8a14b903
CRs-Fixed: 3375254
This reverts commit I440bcfbc3b9699ab42d4304535cc2d86d702d21d.
The "Roc delay set mac issue" is fixed by change
If53d5ee446fc5f4df2fcf117a436133116270b9e
Change-Id: Ica97a9d829e74a8b43030086d478bbfb125a371e
CRs-Fixed: 3381663
Whenever driver add new feature, it increments the feature version
and send it to firmware.
Due to new 11KV feature update, increments the feature version.
Change-Id: Ia840faf85c06a4f33f68f59dadda400c8e91804c
CRs-Fixed: 3381243
Firmware sends the roam scan info tlv to driver during roaming.
Currently, in this tlv, firmware fills scan type as (0-3) and
driver log this as "PARTIAL", "FULL", "NO SCAN" and "Higher Band"
But with new requirement, idle roaming shall only roam to higher band
(2.4 GHz < 5 GHz < 6 GHz) than current band.
1. If current band is 2.4 GHz, it cannot roam to 2.4 GHz.
It can roam to 5 GHz and 6 GHz.
2. If current band is 5 GHz, it cannot roam to 2.4 GHz and 5 GHz.
It can roam to 6 GHz.
So, to add this requirement, firmware introduces new scan type 4 for
which driver need to log.
Change-Id: I80d1c47a434da5009aed4cab08c6eae91bda5b0e
CRs-Fixed: 3379468
API to free the roaming info, fils ie and connect ies is now
present in cmn. Reuse of the same API to optimize the code.
Change-Id: I63b416323b4882ee589941e9b06f45a094b3f800
CRs-Fixed: 3378946
"bad_bssid_counter_thresh" is an ini parameter to specify the threshold
after which the BSSID is in the avoid list should be moved to
deny list, assuming that the AP or the gateway with which the data
stall happened has not recovered, and now the STA got the NUD
failure again with the BSSID.
Currently, in driver sets max value for this ini param as 10.
But for some new requirement, this value is required to 100 as
user does not want any BSSID in reject list.
So, to enable this feature, increase the max value for this param
as 100.
Change-Id: I80e908c82ea74801bfcb04a9669cc4b4589f0dec
CRs-Fixed: 3382136
Add pre-alloc entries for datapath config events
history, so that the memory for this history is
pre-allocated and not freed on every wifi off.
Change-Id: Iae1013c68a77d7da719400579af43369d9663163
CRs-Fixed: 3379157
