Currently, If AP doesn't allow Prohibit to be set and user tries
to enable prohibit, host doesn't send command to FW to enable prohibit
but doesn't send failure status to user space.
Fix is to send failure status to userspace in case prohibit is not enabled.
Change-Id: Ic983b85d27e16314f63c02f88d3b1689d587d622
CRs-Fixed: 3344607
Currently, if SR (Spatial Reuse) is supported by AP and then
STA roams to another AP then host needs to parse SR IE and
send events to userspace and commands to Fw based on below
scenarios:
i.) Roamed AP doesn't support SR: If roamed AP doesn't support
SR then async event with SR disable is required to be sent to
userspace.
ii.) Roamed AP supports SR: If roamed AP supports SR then below
validations are required.
a.) existing thresholds are in range of roamed AP: Send SR enable
command to FW with previous thresholds , as FW disables SR during
roaming.
b.) existing thresholds are not in range of roamed AP: then decision
will be based on whether threshold is provided during SR enable command
or not. If threshold is provided along with SR enable command then send
disable to userspace and in other case update thresholds as per roamed
AP , send async event to userspace with new configured values and send
enable command to fw with new thresholds.
Change-Id: I0c39de349c0f723d49d510c6e8ba09dcb98c6d17
CRs-Fixed: 3316985
Currently, only single pd_threshold is fetched and
treated as SRG and NON-SRG pd threshold instead of
handling both threshold separately.
Fix is to get SRG and NON-SRG pd threshold from
userspace instead of single pd threshold
Change-Id: I2a131ea9040c799bc12a17a9ce42be02da8a717b
CRs-Fixed: 3328189
Remove WMI_PDEV_PARAM_SET_CMD_OBSS_PD_THRESHOLD which is sent to
initialize the hardware registers. The initialization of hardware
registers is done as part of WMI_VDEV_PARAM_SET_CMD_OBSS_PD_THRESHOLD
Change-Id: I272fbd6723836efb9864cb78bdaf3e0eacf45554
CRs-Fixed: 3329913
The following change introduced a new misspelling of "disable", so fix
it.
- Change-Id Ie98a1b8681f41f3a63523ac40b5cfb688a7b0cb0
qcacld-3.0: Handle VENDOR_SUBCMD_SR and operation
Change-Id: I7a06c24cf732b12072377835f01bd50aa5785062
CRs-Fixed: 3319368
The following change introduced a misspelling of "threshold", so fix
it.
- Change-Id Ie98a1b8681f41f3a63523ac40b5cfb688a7b0cb0
qcacld-3.0: Handle VENDOR_SUBCMD_SR and operation
Change-Id: I255ef45d9978ce777a41564f0d05e6d99efe5a4b
CRs-Fixed: 3319363
Check for HESIGA_VAL15_ALLOWED bit before enabling SR prohibit
in SR control field
Change-Id: Ie902941c7642d76901adbf5d685265c0552a814c
CRs-Fixed: 3308160
Add async event for Spatial Reuse and also send Spatial Reuse
enable / disable event to upper layer due to same MAC concurrency.
Change-Id: Idcb5b99e39f1810e63ae7ac1e8d2eab6028a163f
CRs-Fixed: 3307801
Add check for concurrency with SR, if SR with concurrency
is not enabled then disable the SR on existing VDEV as soon as
new VDEV is up.
When this new VDEV is disconnected, then enable back the SR on
the previous VDEV.
Change-Id: Id6aee592b889bb7006efb44420e6d272212e13ba
CRs-Fixed: 3306181
Send WMI_PDEV_PARAM_SET_CMD_OBSS_PD_THRESHOLD during PDEV
init with disabled PD-Threshold value to initialize SR related
registers in HW.
Change-Id: I49e73c76974e098b6dfbf647a898b53abf8ea2ba
CRs-Fixed: 3306179
Add below two enhancements for SAP
1. Spatial Reuse enabled in single MAC concurrency
2. Set bit HESIGA_Spatial_reuse_value15_allowed in SRP IE
Change-Id: Id2d3d04ae1b3b9a2e6d84f30749b577bc7b79061
CRs-Fixed: 3305447
Add support to parse VENDOR_SUBCMD_SR and to parse
nested attributes OPERATION and PARAMS and to handle
ENABLE operation, Disable operation and prohibit
operation. Enable opeartion may have PD threshold
or in case vendor command doesn't provide PD threshold
host will send PD threshold advertised by AP.
Change-Id: Ie98a1b8681f41f3a63523ac40b5cfb688a7b0cb0
CRs-Fixed: 3299042
