Tamizh Chelvam Raja <quic_tamizhr@xxxxxxxxxxx> wrote: > There are two types of 160 MHz spectral scan support mentioned below > > 1. Fragmented approach > 2. Single event approach > > In this fragmented approach, single 160 MHz will be split as two > 80 MHz buffer. First fft sample buffer will contain spectral scan > result of primary 80 MHz and the second fft sample buffer will contain > secondary 80 MHz and here cfreq1 and cfreq2 will be mentioned. > In case of 160 MHz on 36th channel will contain cfreq1 as 5210 and > cfreq2 as 5290. Chipsets which support this approach are IPQ8074/IPQ6018. > > Replacing freq1 with freq2 in every secondary sepctral scan event to > distinguish between two different 80 MHz spectral event data. > > In the 2nd approach each fft sample buffer will contain spectral scan > result for whole 160 MHz by mentioning cfreq1 as 5250 which is center > frequency of whole 160 MHz. Chipset which support this approach is QCN9074. > > Host will receive spectral event from target for every 5 fft samples. > > Tested-on: IPQ8074 hw2.0 AHB WLAN.HK.2.5.0.1-01120-QCAHKSWPL-1 > Tested-on: QCN9074 hw1.0 PCI WLAN.HK.2.5.0.1-01120-QCAHKSWP > > Signed-off-by: Tamizh Chelvam Raja <quic_tamizhr@xxxxxxxxxxx> > Signed-off-by: Kalle Valo <quic_kvalo@xxxxxxxxxxx> This added a new sparse warning: drivers/net/wireless/ath/ath11k/spectral.c:682:43: warning: incorrect type in assignment (different base types) drivers/net/wireless/ath/ath11k/spectral.c:682:43: expected restricted __be16 [usertype] freq1 drivers/net/wireless/ath/ath11k/spectral.c:682:43: got unsigned short [assigned] [usertype] freq I fixed that in the pending branch. Please remember to use ath11k-check to check your patches. -- https://patchwork.kernel.org/project/linux-wireless/patch/20220725055001.15194-1-quic_tamizhr@xxxxxxxxxxx/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
