From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kalle Valo Date: Thu, 15 Jan 2015 16:30:51 +0200 Subject: [ath9k-devel] [PATCH] ath9k: ignore radar PHY errors when DFS is not enabled In-Reply-To: <3155015.RnApTRDnnO@prime> (Simon Wunderlich's message of "Tue, 13 Jan 2015 12:04:36 +0100") References: <1420822458-531-1-git-send-email-sw@simonwunderlich.de> <2179820.H2CYa3nAla@prime> <54B4F062.2090301@neratec.com> <3155015.RnApTRDnnO@prime> Message-ID: <87ppagnmjo.fsf@kamboji.qca.qualcomm.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org Simon Wunderlich writes: >> I did not dig how the hw->conf.radar_enabled flag is set in monitor mode, >> but if it is same as for master (i.e. set for DFS channels), then it would >> be a better approach to prevent calling ath9k_dfs_process_phyerr() >> altogether from ath9k_rx_skb_preprocess() if not set. > > Hm, you mean like - if radar_enabled then dfs_process, otherwise fft_process? > That would might be more elegant indeed ... > > The monitor mode does not have the radar flag enabled, > cfg80211_chandef_dfs_required() returns 0 in this case. So are you going to send v2 or what's the plan? I didn't quite get the conclusion from the discussion. -- Kalle Valo