Aditya Kumar Singh <quic_adisi@xxxxxxxxxxx> writes: > Currently, the DFS CAC time and the usable state of the primary channel in > the channel definition are used to set the CAC_RUNNING flag for the ath12k > radio structure. However, this approach is flawed because there are channel > definitions where the primary channel is not a DFS channel, but the > secondary channel is. For example, in 5 GHz band, channel 36 with 160 MHz > bandwidth. In such cases, the flag is not set correctly and hence places > where this flag is tested will not operate as expected. For example, Rx > packets will not be dropped. > > To fix this issue, use the cfg80211_chandef_dfs_usable() function from > cfg80211, which returns true if at least one channel is in a usable state. > This will ensure the CAC_RUNNING flag is set properly. > > Additionally, update the CAC running debug log message to include the CAC > time in milliseconds and also print the center frequency segment 1. > > Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.3.1-00173-QCAHKSWPL_SILICONZ-1 > > Signed-off-by: Aditya Kumar Singh <quic_adisi@xxxxxxxxxxx> Acked-by: Kalle Valo <kvalo@xxxxxxxxxx> -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
