mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-10-09 05:39:54 -04:00
No description
- C 98.2%
- Assembly 1%
- Makefile 0.3%
- Shell 0.2%
- Python 0.1%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
99d06c14e9
Currently the firmware supports FILS by default, and the kernel and driver have dependencies on the kernel version for FILS support. The PMK info i.e the PMK length and the PMK itself is sent to the firmware as part of roam scan offload params, and are filled from the PMK received from the CFG layer via csr_roam_set_psk_pmk. The PMK and its parameters are received via a vendor command, and called via ops wlan_hdd_set_default_mgmt_key. With the presence of FILS feature, the pmk is filled via hdd_fill_pmksa_info(), which fills the PMK,PMK length to the pmk_cache. It is called via ops wlan_hdd_cfg80211_set_pmksa. But in the NON-FILS case, the PMK, PMK length received from the CFG layer is NULL and zero respectively, and hence the firmware which expects a valid PMK and PMK length gets a PMK as NULL , and the PMK length as zero, which will lead to deletion of the pmk received earlier via vendor command, also a fresh 8-way handshake from the HOST, rather than a 4-way handshake from firmware if the PMK-ID for that particular AP(BSSID) matches the PMK-ID in the AP. Fix is to fill the params of PMK, PMK length in the NON-FILS case too by copying the params received previously via the vendor command, where the params are stored in the session itself. Hence it will fulfill the requirement of the PMK, PMK len from the firmware, and lead to a faster handshake process while re-associating. Change-Id: I4c91cac6bad400c8fa58b2a6ba2b282a3b7f1620 CRs-Fixed: 2243070 |
||
| components | ||
| configs | ||
| core | ||
| uapi/linux | ||
| Android.mk | ||
| Kbuild | ||
| Kconfig | ||
| Makefile | ||
| README.txt | ||
This is CNSS WLAN Host Driver for products starting from iHelium