Aditya Kumar Singh <quic_adisi@xxxxxxxxxxx> writes: > On 6/7/23 18:16, Aditya Kumar Singh wrote: >> Currently channel definition's primary channel's DFS CAC time >> as well as primary channel's state i.e usable are used to set >> the CAC_RUNNING flag for the ath11k radio structure. However, >> this is wrong since certain channel definition are possbile >> where primary channel may not be a DFS channel but, secondary >> channel is a DFS channel. For example - channel 36 with 160 MHz >> bandwidth. >> In such cases, the flag will not be set which is wrong. >> Fix this issue by using cfg80211_chandef_dfs_usable() function >> from cfg80211 which return trues if at least one channel is in >> usable state. >> While at it, modify the CAC running debug log message to print >> the CAC time as well in milli-seconds. >> Tested-on: QCN9074 hw1.0 PCI >> WLAN.HK.2.7.0.1-01744-QCAHKSWPL_SILICONZ-1 >> Signed-off-by: Aditya Kumar Singh <quic_adisi@xxxxxxxxxxx> > Hi Kalle, > > The upstream dependency got merged today. I have sent [v2] of this > series which was just rebased on latest ToT and the [PATCH v2 1/3] got > merged. With this, [PATCH v2 2/3] and [PATCH v2 3/3] are unblocked > now. Thanks, this is helpful. I still need to merge wireless-next into ath-next but hopefully that happens next week. -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
