Fragments are not flushed as part of rekey which
could result in fragments encrypted under different
keys to be reassembled.
Fix is to flush fragments for the peer for which add
key request is received.
Change-Id: I5ab88fd1bc5936e2aa0910f859fa222873d4e295
CVE-Fixed: CVE-2020-24587
Mot-CRs-fixed: (CR)
CRs-Fixed: 2875950
Reviewed-on: https://gerrit.mot.com/1929642
SME-Granted: SME Approvals Granted
SLTApproved: Slta Waiver
Tested-by: Jira Key
Reviewed-by: Bin Liu <liubin7@motorola.com>
Submit-Approved: Jira Key
Mananr.LA.1.0 and Mannar.LA.1.1 will coexist from r1.0_00026
so we use NONHLOS_PLATFORM_COMMON_PATH to distinguish the dirs.
Change-Id: I605b6467f611d7b76891e53b6728dc87b5a2187c
Reviewed-on: https://gerrit.mot.com/1950741
SME-Granted: SME Approvals Granted
SLTApproved: Slta Waiver
Tested-by: Jira Key
Reviewed-by: Bin Liu <liubin7@motorola.com>
Submit-Approved: Jira Key
Copy qca_cld3_wlan.ko.unstripped and WLAN_MERGED.elf files to out
symbols folder during build time. This will save significant time
to fetch the unstripped and elf files during Kernel panic analysis
by avoiding repo Sync and rebuilding the image on which issue happened.
Change-Id: I5b0a7ca71eb4bd909fcec5b0bc676a5b296b0eec
Reviewed-on: https://gerrit.mot.com/1805423
SME-Granted: SME Approvals Granted
SLTApproved: Slta Waiver
Tested-by: Jira Key
Reviewed-by: Bin Liu <liubin7@motorola.com>
Submit-Approved: Jira Key
1. Compatible with utag that only has one MAC address
2. For the generated MAC address from serialno, set the provisioned mac
address as the custom mac address
Change-Id: I80e96dd906c32411a42e875447504baadd66d4b6
Signed-off-by: sunyue5 <sunyue5@motorola.com>
Reviewed-on: https://gerrit.mot.com/1744536
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Sireesha Kosuri <sireeshak@motorola.com>
Reviewed-by: Zhilu Yin <yinzl1@motorola.com>
Submit-Approved: Jira Key
7250 products will use the same WLAN version on R WLAN.HL.3.3.1.
Only copy this version.
Change-Id: I8d97d00a5271f23b7723020d5740e4677f51a338
Signed-off-by: Daniel Finimundi <danielrf@motorola.com>
Reviewed-on: https://gerrit.mot.com/1687654
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Yinjun Chen <a7301c@motorola.com>
Submit-Approved: Jira Key
Remove wifimacaddr from android ro.boot property set as this property
is not required and just leaks information.
Change-Id: If097394bc4e9dff819fd871bcff66575a4db04c7
Reviewed-on: https://gerrit.mot.com/1714017
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Reviewed-by: Sireesha Kosuri <sireeshak@motorola.com>
Reviewed-by: Prashanth Chakravarthy <a19110@motorola.com>
Tested-by: Jira Key
Submit-Approved: Jira Key
(CR) add wifi tx pwr limit cmd for mimo device
(CR) add wifi mimo tx pwr limit cmd under softap mode
Per RF team req, add cmd to call QCom wmi api, so we can change
TX power limit values of each ANT channel.
add sub ioctl for wifi mimo tx pwr limit settings under softap mode
reworked for Android R.
Change-Id: Ibafe21c99b6f91e6ddf881a6109cb1a478e9284f
In the current infrastructure , “setPowerSave false” is known for DHCP
start and “setPowerSave true” for DHCP stop. Thus, the BT Coex will give
preference to Wi-Fi during this period of DHCP start – stop.
This setPowerSave false / true interface is not only triggered on DHCP
start / stop but this is also a public API which can be triggered by the
applications when they want the Wi-Fi system to go in to
WIFI_MODE_FULL_HIGH_PERF. Thus , the “setpowersave false“ will be
triggered but not the corresponding “true” . As a result , the BT Coex
module shall assume that the DHCP is still in progress and keeps giving
preference to Wi-Fi.
and WifiNative.setBluetoothCoexistenceMode() is invoked only when DHCP
start & stop, hence we can use bt_coex_mode_set to deterministically
signify the DHCP start / Stop and send DHCP start / stop indication to FW
Change-Id: If5cca595aec22b7a10af4b127a5f75118d1ddc26
Signed-off-by: liubin7 <liubin7@motorola.com>
Reviewed-on: https://gerrit.mot.com/1464100
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Submit-Approved: Jira Key
Copy qca_cld3_wlan.ko.unstripped and WLAN_MERGED.elf files to out
symbols folder during build time. This will save significant time
to fetch the unstripped and elf files during Kernel panic analysis
by avoiding repo Sync and rebuilding the image on which issue happened.
This is a squash for all Helium products.
Change-Id: I5a4ce7b77e9ead134ae969efa46bbecedc0f9d37
We do not enable CH14 for JAPAN on all of our
products and have disabled it on 8998 as well.
QC SR : 04679882
Change-Id: Ibd37d238877c81b180dcd1e3e72e84ef4d868592
Signed-off-by: vineetv <vineetv@motorola.com>
Reviewed-on: https://gerrit.mot.com/1642393
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Prashanth Chakravarthy <a19110@motorola.com>
Submit-Approved: Jira Key
Copy qca_cld3_wlan.ko.unstripped to out symbols folder during build time.
This will save significant time to fetch the unstripped during Kernel panic analysis
by avoiding repo Sync and rebuilding the image on which issue happened.
Change-Id: I1fc720560e0f74178Montana0ef604413e5b553dbd2f
Reviewed-on: https://gerrit.mot.com/1119046
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Prashanth Chakravarthy <a19110@motorola.com>
Submit-Approved: Jira Key
Reviewed-on: https://gerrit.mot.com/1456501
Submit-Approved: Raja Phani K <a16821@motorola.com>
For the concurrency mode sta+sap , we need 2 mac addresses
DUT is generating only 1 mac address based on serial number
added the code to generate the remaining mac addresses
Change-Id: I6d2880f746656d332ace67417edb29ad8b97b44a
Reviewed-on: https://gerrit.mot.com/1481319
Reviewed-by: Prashanth Chakravarthy <a19110@motorola.com>
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Submit-Approved: Jira Key
Moving this log as debug logs by Motorola as
Qualcomm need to support multiple configuration.
Change-Id: Ic7dbfe906b844d23f159e73d2795159158e4dbcc
Reviewed-on: https://gerrit.mot.com/1469662
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Prashanth Chakravarthy <a19110@motorola.com>
Submit-Approved: Jira Key
Since we use wrqu structure to pass data from
qsap, use copy_from_user function to avoid
data corruption.
Change-Id: Ic5f4f8631246c932432fc2317829534b521ec438
Reviewed-on: https://gerrit.mot.com/1456951
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Prashanth Chakravarthy <a19110@motorola.com>
Submit-Approved: Raja Phani K <a16821@motorola.com>
Propogate (CR) : get correct tx power from ioctl.
Restructured based on the 8250 files
Change-Id: I2216a0442cbb8dbb7fd9a1fcbbed5be9bec177ac
Reviewed-on: https://gerrit.mot.com/1456950
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Prashanth Chakravarthy <a19110@motorola.com>
Submit-Approved: Raja Phani K <a16821@motorola.com>
The ioctl handling needs to be differentiated between
calls made by Mot code and iwpriv code since they
fill in different parameters.
Change-Id: If5276c14e20f87c88123c8d3c68849ac8f4e6173
Reviewed-on: https://gerrit.mot.com/1456948
SME-Granted: SME Approvals Granted
SLTApproved: Slta Waiver
Reviewed-by: Prashanth Chakravarthy <a19110@motorola.com>
Tested-by: Jira Key
Submit-Approved: Raja Phani K <a16821@motorola.com>
Ioctls value was being filled up with wrq data structure in
softap sdk, but extra parameter was being read from driver.
Fix to read the wrq data structure in driver
Change-Id: I06d8be4e3665bad937614fcb579c36f5f1159e10
Reviewed-on: https://gerrit.mot.com/1456947
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Prashanth Chakravarthy <a19110@motorola.com>
Submit-Approved: Raja Phani K <a16821@motorola.com>
iwpriv tool uses extra parameter whereas Mot
ioctl uses wrqu data structure. Need to differentiate
between the two to resolve panic
Change-Id: Icb1c9e4f75ad1f89f43ff2be5fc7f551f3176851
Reviewed-on: https://gerrit.mot.com/1456946
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Prashanth Chakravarthy <a19110@motorola.com>
Submit-Approved: Raja Phani K <a16821@motorola.com>
Create sar_mhs and sar_sta sysfs entries for recording wlan states
for SAR cutback. The WLAN driver does not care about these entries
but they are needed as IPC over to the mdmcutback daemon.
Change-Id: I277f7c68e3b74557edb6ff82fa0224d1f470fd95
Reviewed-on: https://gerrit.mot.com/1264155
SME-Granted: SME Approvals Granted
SLTApproved: Slta Waiver
Tested-by: Jira Key
Reviewed-by: Binesh Balasingh <binesh@motorola.com>
Submit-Approved: Jira Key
Reviewed-on: https://gerrit.mot.com/1456500
Reviewed-by: Prashanth Chakravarthy <a19110@motorola.com>
Submit-Approved: Raja Phani K <a16821@motorola.com>
In WLAN driver for Helium family, QC has updated hdd_context_t
structure and removed intfMacAddr variable. As a result,
with Motorola MAC address changes, compilation was failing.
Replaced intfMacAddr with new provisioned and derived variables
to read and use MAC address from UTAG properly.
Updated the MOT OUI with latest MOT OUI values.
Change-Id: I78e942aefc5b802e6297402c796d5d002b6d955a
Reviewed-on: https://gerrit.mot.com/1196122
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Prashanth Chakravarthy <a19110@motorola.com>
Submit-Approved: Yun Ma <yunma@motorola.com>
- Read MAC Address from UTAG
- Generate new MAC address from serial number, if UTAG
is not programmed with MAC addresses in Factory.
Port changes from (CR) to new Helium platform(sm6150).
Change-Id: If6d2e532907ff0cd267262710b3c694bf73c9129
Reviewed-on: https://gerrit.mot.com/1257719
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Bin Liu <liubin7@motorola.com>
Submit-Approved: Jira Key
Changes based on new TLV2 format to support 12M wlan radiated
power test on Production SW.
Change-Id: I90e2dfe8d2828f054cb5f540d51e3ef71d5112a5
Reviewed-on: https://gerrit.mot.com/983481
SLTApproved: Slta Waiver <sltawvr@motorola.com>
SME-Granted: SME Approvals Granted
Reviewed-by: Santhosh Kumar Gillella <santhoshg@motorola.com>
Tested-by: Jira Key <jirakey@motorola.com>
Submit-Approved: Jira Key <jirakey@motorola.com>
SAP is allowed to come up on SCC with a STA operating
in 6 GHz only if the STA is on a PSC channel in VLP mode.
Therefore, filter out all 6 GHz channels from the PCL if
the STA operates on any non-VLP mode. Also, in case of
VLP mode, filter out non-PSC channels.
Change-Id: I37d9a510db3647fc07858af99eb614ebe824cc78
CRs-Fixed: 3206471
If user configure to not use 40 MHz in 2.4 GHz, then avoid setting
40 MHz capability and use cb mode as
WNI_CFG_CHANNEL_BONDING_MODE_DISABLE for 2.4 GHz.
Change-Id: I4e9153e211e02f6b959e16dad4573c2b490cb215
CRs-Fixed: 3584510
When send assoc req frame, if the length for extended capabilities
IE is zero, but present field is non-zero, it will cause assoc req
frame malformed issue.
Fix is to set present field value to zero when the length for
extended capabilities IE is zero.
Change-Id: Ie8826e6cfb1fc3a44ee52115ad4482e040f2c38a
CRs-Fixed: 3085943
The 6GHz HE capability macros were backported from kernel version 5.8
into 5.4, so change the check for kernel version to simply check for
the macro definition itself.
Change-Id: I86a9dfa964356ba65bd21ffef802042d442356bc
CRs-fixed: 2960286
New checks have been added in userspace to verify the 6GHz HE
capabilities before allowing the connection. These capabilities
are not currently being shared by host. Add logic to send the
6GHz HE capabilities to userspace.
Also, add APIs to get capabilities from MLME component.
Change-Id: I3d2bbe0d87be6094b6fc74ce01d0e418873cbc6f
CRs-fixed: 2931130
User may set the ini param g_sta_sap_scc_on_lte_coex_chan=1 if SAP
is allowed to come up on unsafe channels. Currently, this doesn't
cover the below case,
1. SAP is enabled on a 5 GHz channel in a non-DBS platform
2. Concurrent STA enabled and connected it to an AP that's in
unsafe channel.
3. SAP doesn't move to the STA channel though the ini to enable
force SCC(gWlanMccToSccSwitchMode) is set and it's a non-DBS
platform as the target channel(STA channel) is unsafe channel.
Allow SAP to move to unsafe STA channel if the ini
g_sta_sap_scc_on_lte_coex_chan is set to true.
Change-Id: I3e2b8ae57e843a938e4799f473da87664dbabb85
CRs-Fixed: 3609503
Add sanity check for index with NUM_CHANNELS and pcl_sz
when add 2.4 GHz channel list.
Change-Id: I04ac1bcdb6720a4740be7c2f5e08f76b3c34d8c4
CRs-Fixed: 3025000
Skip the FISA aggregation and drop the frame if the reo destination
indication is zero in the packet TLVs.
Change-Id: I9bd02652bf321202f6b59e6da98fc6959ab93413
CRs-Fixed: 3426355
In populate_dot_11_f_ext_chann_switch_ann API, will read current country
code from mac context which is not have the updated country code.
So, read the current country code directly from regulatory API,
wlan_reg_read_current_country.
Remove unused variables mac->scan.countryCodeCurrent,
mac_ptr->scan.countryCodeDefault and tagCsr11dinfo->countryCode.
Change-Id: Ice64ef1be5b775125ff3bcacfcab7684c6833cad
CRs-Fixed: 3529808
For STA+SAP/GO concurrency support from GUI, In case if
START/STOP AP/GO request comes just before the SAE
authentication completion on STA, SAE AUTH REQ waits for
START/STOP AP RSP and START/STOP AP RSP waits to complete
SAE AUTH REQ.
Driver completes START/STOP AP RSP only upon SAE AUTH REQ
timeout(5 sec) as start/stop ap will be in serialization
pending queue, and SAE auth sequence cannot complete as
hostap thread is blocked in start/stop ap cfg80211 ops.
To avoid above deadlock until SAE timeout, abort the SAE
connection immediately and complete START/STOP AP/GO asap
so that the upper layer can trigger a fresh connection
after START/STOP AP/GO completion.
Change-Id: I96de1bb27dfc669ccf920a90cf86a3cb54e68354
CRs-Fixed: 3452943
The AP adds OMN IE in the assoc response, and changes
its operating channel width during association. The
STA must move to this new channel width and update it
to the firmware during peer assoc. Since, the STA
doesn't update the channel width properly, it leads
to retries in the higher bandwidth where the AP is
not currently operating.
The VHT channel width calculation in the host driver
is not equipped to handle the new VHT OP IE definition.
Differentiate the VHT operating channel width field in
the VHTOP IE based on the ccf1.
Change-Id: Ibc3dc91ecc091a307244e3e1359dfe9e4520f277
CRs-Fixed: 3205020
