linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lorenzo Bianconi <lorenzo@kernel.org>
To: Sven Eckelmann <sven@narfation.org>
Cc: nbd@nbd.name, lorenzo.bianconi@redhat.com,
	linux-wireless@vger.kernel.org, sean.wang@mediatek.com,
	deren.wu@mediatek.com
Subject: Re: [PATCH] mt76: mt7921: toggle runtime-pm adding a monitor vif
Date: Tue, 11 Jan 2022 13:45:04 +0100	[thread overview]
Message-ID: <Yd170LnF5Y2D8by5@lore-desk> (raw)
In-Reply-To: <8554350.NRS6bbiA14@ripper>

[-- Attachment #1: Type: text/plain, Size: 926 bytes --]

> On Tuesday, 11 January 2022 10:34:17 CET Lorenzo Bianconi wrote:
> > Toggle runtime-pm and deep-sleep configuration adding/removing
> > a montior vif in order to forward all tx/rx frames to mac80211.
> 
> Tested-by: Sven Eckelmann <sven@narfation.org>
> 

ack, thx for testing.

> So monitor interface now works out of the box for me. Only receiving of 
> beacons (and maybe more?) is not possible with 
> 
>     mt7921e 0000:05:00.0: ASIC revision: 79610010
>     mt7921e 0000:05:00.0: HW/SW Version: 0x8a108a10, Build Time: 20211222190839a
>     mt7921e 0000:05:00.0: WM Firmware Version: ____010000, Build Time: 20211222190917

adding monitor vif we disable beacon filter, so I guess we should receive them.
@Sean, Deren: any hint about it? does the fw support this configuration?
I checked MT_WF_RFCR(0) register, and it is 0x2 adding a monitor vif.

Regards,
Lorenzo

> 
> Thanks,
> 	Sven



[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2022-01-11 12:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-11  9:34 [PATCH] mt76: mt7921: toggle runtime-pm adding a monitor vif Lorenzo Bianconi
2022-01-11 12:31 ` Sven Eckelmann
2022-01-11 12:45   ` Lorenzo Bianconi [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Yd170LnF5Y2D8by5@lore-desk \
    --to=lorenzo@kernel.org \
    --cc=deren.wu@mediatek.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lorenzo.bianconi@redhat.com \
    --cc=nbd@nbd.name \
    --cc=sean.wang@mediatek.com \
    --cc=sven@narfation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).