Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 843CEC433F5 for ; Sat, 4 Dec 2021 00:58:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1383940AbhLDBBR (ORCPT ); Fri, 3 Dec 2021 20:01:17 -0500 Received: from mailgw02.mediatek.com ([210.61.82.184]:53308 "EHLO mailgw02.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1383932AbhLDBBP (ORCPT ); Fri, 3 Dec 2021 20:01:15 -0500 X-UUID: dee51072620a46068c8b402c3580d68b-20211204 X-UUID: dee51072620a46068c8b402c3580d68b-20211204 Received: from mtkcas10.mediatek.inc [(172.21.101.39)] by mailgw02.mediatek.com (envelope-from ) (Generic MTA with TLSv1.2 ECDHE-RSA-AES256-SHA384 256/256) with ESMTP id 294837326; Sat, 04 Dec 2021 08:57:48 +0800 Received: from mtkexhb01.mediatek.inc (172.21.101.102) by mtkmbs07n1.mediatek.inc (172.21.101.16) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Sat, 4 Dec 2021 08:57:26 +0800 Received: from mtkcas10.mediatek.inc (172.21.101.39) by mtkexhb01.mediatek.inc (172.21.101.102) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Sat, 4 Dec 2021 08:55:05 +0800 Received: from mtkswgap22.mediatek.inc (172.21.77.33) by mtkcas10.mediatek.inc (172.21.101.73) with Microsoft SMTP Server id 15.0.1497.2 via Frontend Transport; Sat, 4 Dec 2021 08:55:04 +0800 From: To: CC: , , , , , "Sean Wang" Subject: Re: mt76: MT7921K monitor mode not working Date: Sat, 4 Dec 2021 08:55:04 +0800 Message-ID: <1638579304-17794-1-git-send-email-sean.wang@mediatek.com> X-Mailer: git-send-email 1.7.9.5 In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain X-MTK: N Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org From: Sean Wang >> From: Sean Wang >> >> >> On Thursday, 2 December 2021 23:13:31 CET Lorenzo Bianconi wrote: >> >> > IIRC you need to disable runtime-pm and deep-sleep to proper >> >> > enable monitor >> >> > mode: >> >> > >> >> > echo 0 > /sys/kernel/debug/ieee80211/phy/mt76/runtime-pm >> >> > echo 0 > /sys/kernel/debug/ieee80211/phy/mt76/deep-sleep >> >> > >> >> > Can you please give it whirl? >> >> >> >> Jan gave me the card. I've set it to a rather busy channel (2.4GHz >> >> channel 11), created a monitor interface, attached tcpdump and then >> >> waited what happens. I didn't get anything and then I've tried to >> >> set runtime-pm and deep- sleep to 0. This didn't change the >> >> behavior for me at lot. I saw two packets and then it went silent again. >> >> >> >> I wanted to try the same on a different card (ath11k) in the same >> >> system. But it crashed my complete system - so I had to recreate >> >> the test setup. This time, I've set runtime-pm + deep-sleep to 0 >> >> before creating mon0. After doing this, it seemed to work. >> > >> >interesting, adding Sean to the loop here. >> >It seems the fw is mainting a different state in this case. >> >> fw cannot receive any frame on monitor mode in deeply doze mode >> >> so it seemed to me we need a patch to explicitly disable pm runtime in driver when monitor interface is enabled until it is being disabled. > >ack, I agree, but I guess the point here is what is the difference (from the fw pov) if you disable runtime-pm/deep-sleep before/after the vif is added. I guess it is supposed to be the same, right? yes, it is supposed to be the same. > >Regards, >Lorenzo > >> >> > >> >@Sean: any pointers? >> > >> >Regards, >> >Lorenzo >> > >> >> >> >> Kind regards, >> >> Sven >> > >> >