From: "Nicolas Escande" <nico.escande@gmail.com>
To: "Karthikeyan Periyasamy" <quic_periyasa@quicinc.com>,
<ath12k@lists.infradead.org>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 0/7] wifi: ath12k: Add monitor interface support on QCN9274
Date: Fri, 17 Jan 2025 10:46:28 +0100 [thread overview]
Message-ID: <D7493TJ2Q2YJ.2EVCWPQR58U4A@gmail.com> (raw)
In-Reply-To: <d9181c82-ffb1-e8de-c5c6-f58b73f9291f@quicinc.com>
On Fri Jan 17, 2025 at 5:37 AM CET, Karthikeyan Periyasamy wrote:
> On 1/15/2025 11:25 PM, Nicolas Escande wrote:
> > On Tue Jan 7, 2025 at 3:10 AM CET, Karthikeyan Periyasamy wrote:
[...]
> > I applied it on top of ath-pending-202501150104 + the "ath12k: Add peer extended
> > Rx statistics debugfs support" and now 'iw dev wlan0 station dump' shows me
> > that the RSSI value seems to not be updated anymore after I stop a monitor
> > interface on the same phy.
> >
> > Steps to reproduce:
> > iw phy phy0 interface add mon0 type monitor
> > ip link set mon0 up
> > # then just for 1 sec but it might not be usefull at all
> > tcpdump -nepi mon0
> > ip link set mon0 down
> > watch -n1 iw dev wlan0 station dump
> > # 'signal' seems to not be updating anymore, maybe some other fields too ?
> >
>
> Not able to find the wlan0 interface details from the above steps ?
Arf maybe I wasn't clear, my bad.
I have a running AP on wlan0. I constantly monitor connected stations infos
using 'iw dev wlan0 station dump' on the side in another terminal, and then I
add a monitor interface with the above steps, and thats when I see that the
stations connected to my AP have frozen values in station dump.
I suspect that ath12k_dp_tx_htt_rx_monitor_mode_ring_config() should reset the
rx filters to ath12k_mac_mon_status_filter_default when disabling monitor. But
I'm not so sure, you guys know better.
prev parent reply other threads:[~2025-01-17 9:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 2:10 [PATCH 0/7] wifi: ath12k: Add monitor interface support on QCN9274 Karthikeyan Periyasamy
2025-01-07 2:10 ` [PATCH 1/7] wifi: ath12k: fix link valid field initialization in the monitor Rx Karthikeyan Periyasamy
2025-01-07 2:10 ` [PATCH 2/7] wifi: ath12k: Add extra TLV tag parsing support in monitor Rx path Karthikeyan Periyasamy
2025-01-07 2:10 ` [PATCH 3/7] wifi: ath12k: Avoid fetch Error bitmap and decap format from Rx TLV Karthikeyan Periyasamy
2025-01-07 2:10 ` [PATCH 4/7] wifi: ath12k: Replace band define G with GHZ where appropriate Karthikeyan Periyasamy
2025-01-07 2:10 ` [PATCH 5/7] wifi: ath12k: change the status update in the monitor Rx Karthikeyan Periyasamy
2025-01-07 2:10 ` [PATCH 6/7] wifi: ath12k: Avoid packet offset and FCS length from Rx TLV Karthikeyan Periyasamy
2025-01-07 2:10 ` [PATCH 7/7] wifi: ath12k: add monitor interface support on QCN9274 Karthikeyan Periyasamy
2025-01-17 11:33 ` Nicolas Escande
2025-01-17 13:06 ` Karthikeyan Periyasamy
2025-01-17 13:20 ` Nicolas Escande
2025-01-21 9:12 ` Karthikeyan Periyasamy
2025-01-21 9:49 ` Nicolas Escande
2025-01-15 17:55 ` [PATCH 0/7] wifi: ath12k: Add " Nicolas Escande
2025-01-15 19:56 ` Jeff Johnson
2025-01-16 13:51 ` Nicolas Escande
2025-01-17 4:37 ` Karthikeyan Periyasamy
2025-01-17 9:46 ` Nicolas Escande [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=D7493TJ2Q2YJ.2EVCWPQR58U4A@gmail.com \
--to=nico.escande@gmail.com \
--cc=ath12k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_periyasa@quicinc.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.