Reduce disruptions caused by radar events
General
When using DFS channel (specially on backhauls) and radar comes, everyone need to switch away from that channel. This causes many disruptions to customer network and bad user experience as it can take a lot of minutes to stabilize the customer network (think about customers with many nodes in their home/office/…).
This feature improves the user experience and reduce disruptions caused by radar events. OpenSync will select DFS runaway channel and insert into WiFi driver. It can be different non-DFS channel or another DFS channel on different frequency with CAC already calculated.
Northbound API
No changes and using existing WiFi_Radio_Config table and fields.
Southbound API
Qualcomm
To communicate with the driver, field OL_ATH_PARAM_NXT_RDR_FREQ is used. One might ask, that “frequency” sounds like incomplete “channel” information. To tackle that problem, field OL_ATH_PARAM_NXT_RDR_WIDTH has been added next to it. To utilize width parameter, adequate patch has been added to ieee80211_set_nxt_radar_frequency function.
OpenSync will set/get those two parameters.
Broadcom
The driver is controlled using wl, this command has option dfs_channel_forced per physical radio. This command accepts all available “channels” for wl. Use wl -i wlX chanspecs to list all. Each is a combination of primary frequency and width. No patches to the driver required.
OpenSync will supply use this option of wl (read and write).
Requirements
Feature is currently limited to chip vendor as Qualcomm and Broadcom. Other SoC can be extended by OpenSync contribution.
Qualcomm patch was been upstreamed and you can request it from Qualcomm or receive it as part of OpenSync SDK overlay.