aboutsummaryrefslogtreecommitdiffstats
path: root/wpa_supplicant/ctrl_iface.c
diff options
context:
space:
mode:
authorVasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com>2017-03-08 05:13:17 (GMT)
committerJouni Malinen <j@w1.fi>2017-03-09 15:01:50 (GMT)
commit7cbb5f1a44e73752c576e259386c541905023dc3 (patch)
tree9380f786112b3e82d30ab2f1e60a29e2de560296 /wpa_supplicant/ctrl_iface.c
parent62c8c7f721563d0417fa10efb2b7faa6ee57034b (diff)
downloadhostap-7cbb5f1a44e73752c576e259386c541905023dc3.zip
hostap-7cbb5f1a44e73752c576e259386c541905023dc3.tar.gz
hostap-7cbb5f1a44e73752c576e259386c541905023dc3.tar.bz2
DFS: Handle pre-CAC expired event
As FCC DFS requirement does not explicitly mention about the validity of the (pre-)CAC when channel is switched, it is safe to assume that the pre-CAC result will not be valid once the CAC completed channel is switched or radar detection is not active on the (CAC completed) channel within a time period which is allowed (10 seconds - channel switch time) as per FCC DFS requirement. Use the new driver event to allow the driver to notify expiry of the CAC result on a channel. Move the DFS state of the channel to 'usable' when processing pre-CAC expired event. This means any future operation on that channel will require a new CAC to be completed. This event is applicable only when DFS is not offloaded to the kernel driver. Signed-off-by: Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com>
Diffstat (limited to 'wpa_supplicant/ctrl_iface.c')
0 files changed, 0 insertions, 0 deletions