Thread (13 messages) 13 messages, 3 authors, 2021-12-08

Re: [PATCH 1/3] ath11k: add htt cmd to enable full monitor mode

From: Kalle Valo <hidden>
Date: 2021-09-28 06:56:51
Also in: ath11k

akolli@codeaurora.org writes:
On 2021-09-24 17:12, Kalle Valo wrote:
quoted
Jouni Malinen [off-list ref] writes:
quoted
From: Anilkumar Kolli <redacted>

Add a new hw_param full_monitor_mode to enable full monitor support
for
QCN9074. HTT_H2T_MSG_TYPE_RX_FULL_MONITOR_MODE cmd is sent to the
firmware to enable the full monitor mode.
Nowhere it's explained what "full monitor mode" means from an user's
point of view. Can someone give a high level summary what advantages
this feature has? For example, more frames delivered to user space or
what?
Yes, more frames delivered with full monitor mode. The advantage with
full monitor mode is, hardware has status buffers available for all
the MPDUs in mon_dst_ring. Both status buffer and MPDUs from
mon_dst_ring is used to build the frame.
Users, and developers outside of the wireless domain, have no clue what
"MPDUs in mon_dst_ring" means, just as an example. Can you give a higher
level summary of this feature and what benefit it brings, please? I'll
then add that to the commit log.

For example, what kind of frames are we now able to deliver to the user
space (which we before couldn't) and are there still some types of
frames which we are not delivering?

In other words, instead of technical low level jargon I'm looking for a
summary in plain english which is understandable by everyone.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help