99708500c0
Scenario here is: 1. AP configured in 320 MHz 2. Set country code = KR in DUT, It means DUT does not support connection in 320 MHz. 3. Trigger connection with AP, while processing driver founds, country code is KR, so downgraded connected channel with to next max supported channel width as per regulatory rule (which is 160 MHz here) and successfully associated with AP in 160 MHz. 4. After connection Host receives “get_channel” request from kernel. 5. Host gets currently connected BSSID and fetch corresponding channel information from scan cache. 6. As scan cache gets updated via beacon/probe response from AP and here advertise beacon/probe response in 320 MHz. This results value of channel width for connected BSSID is 320 MHz and same host fill in get_channel response. 7. By this time driver connected in 160 MHz and connected channel width indicated to kernel is 320 MHz. Due to mismatch in channel width, kernel triggered disconnection. Fix is to update connected channel width in response to “get_channel” request. Change-Id: I7c4a262d337f9deb8cb4436cae537d0069a98de1 CRs-Fixed: 3810073
This is CNSS WLAN Host Driver for products starting from iHelium