mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-10-12 07:37:31 -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 |
|---|---|---|
379e05c97a
In the case of SAP restart due to a RADAR, or force SCC due to STA vdev formed, in the SAP restart path the driver updates the SAP channel in the global AP context, and then sends the command to change the channel to south bound layers to process, which may reject or accept the command. If the command has been accepted, the channel in the global config would be the same as the channel configured in the restart path, but for a case where the command was rejected by the south bound, due to a concurrency check, or other reasons the SAP remains on the previous channel in SCC, or MCC, with the STA interface, but the channel in the global config is same as that given in the restart path, so the real operating channel, and the config channel are different. Because of this if a fresh bringup of some vdev is to be done according to the channel of the SAP, that would fail in some cases ( SAP on DFS channel, and STA coming, so the driver would reject MCC, and SCC) which could be avoided if the channel of the SAP wouldnt be configured in the restart path, and would be configured in the callback of SAP. Also the secondary channel of the SAP was configured as the secondary channel configured at time of fresh SAP bringup, hence the sec channel isn't updated after every restart of SAP. Fix is to configure the channel of in the global AP context only when the SAP START or CHANNEL CHANGE event comes for the SAP. Also update the secondary channel after the CSA. Change-Id: I6cbc31cae4958c0d7da79d4640e5ad8b1ce98338 CRs-Fixed: 2355420 |
||
| components | ||
| configs | ||
| core | ||
| os_if | ||
| uapi/linux | ||
| Android.mk | ||
| Kbuild | ||
| Kconfig | ||
| Makefile | ||
| README.txt | ||
This is CNSS WLAN Host Driver for products starting from iHelium