diff options
| author | Jeff Johnson <jjohnson@codeaurora.org> | 2018-07-17 20:15:56 -0700 |
|---|---|---|
| committer | Gerrit - the friendly Code Review server <code-review@localhost> | 2018-08-01 08:35:41 -0700 |
| commit | f3776d790e653346c517a54657be2341684f7d8f (patch) | |
| tree | 0b8110d1abcdbf2dbdb1fbd2fba5e020b0382aa3 /Kconfig | |
| parent | 8cc63a115748263eace2a212c352793e9b19702c (diff) | |
| download | qcacld-f3776d790e653346c517a54657be2341684f7d8f.tar.gz | |
qcacld-3.0: Implement WLAN_FEATURE_SARV1_TO_SARV2
SARv1 to SARv2 upgrade can have the following problem:
1) Userspace application was written to use SARv1 BDF entries
2) Product is configured with SAR V2 BDF entries
So introduce WLAN_FEATURE_SARV1_TO_SARV2 which has the logic:
If this feature is enabled, and if the firmware is configured with SAR
V2 support, and if the incoming request is to enable a SAR V1 BDF
entry, then the WMI command is generated to actually configure a SAR
V2 BDF entry.
CRs-Fixed: 2282071
Change-Id: I1f4c65d0315b56af6646ca1d5491eaa9c1f732a5
Diffstat (limited to 'Kconfig')
0 files changed, 0 insertions, 0 deletions