f6fa6b6729
Hopping radar happens on whole band, hope all DFS sub channels are put to NOL, but F/W only reports single radar event on special freq to host. When DFS puncture enabled, sub channel marking is enabled, host only put single affected 20M sub channel to NOL instead of all current bonded sub channel, AP still stays on current freq for valid puncture bitmap instead of leave DFS freq. If the radar is a frequency hopping radar that truly hops over entire DFS band, then the AP and clients are best served by moving out of the DFS band. But it could well be that only part of the band is used. It is difficult to find product specifications with info on the total bandwidth. Mostly military systems use frequency hopping to avoid jamming. So a middle ground would be to put full bandwidth of current AP to NOL for FCC type 6 frequency hopping radar. When frequency hopping radar happens, F/W set flag that full bandwidth need put to NOL in new added tlv radar_flags of event WMI_PDEV_DFS_RADAR_DETECTION_EVENT, When find the flag is set, host will put full bandwidth of current AP to NOL even sub channel marking is enabled. To avoid compatibility issue between old/new F/W and new/old host, add a F/W service bit wmi_service_radar_flags_support and host service flag is_full_bw_nol_supported. If the wmi_service WMI_SERVICE_RADAR_FLAGS_SUPPORT is enabled by FW, host shall set/unset a bit in the host service flag is_full_bw_nol_supported based on host capabilities. This host service flag is then sent to FW via WMI_INIT_CMDID. Change-Id: I6e280ca4ab00dce97c5aec90c7a4b4fc7c4a440a CRs-Fixed: 3595476
This is CNSS WLAN Host Driver for products starting from iHelium