Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.38 as permitted sender) client-ip=23.128.96.38;
Message-ID: <c84bf2bf-7af5-49d4-b3a4-dba7abb8fca6@gmail.com>
Date:   Tue, 17 Oct 2023 09:56:35 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: RX multicast action frames (ath10k)
Content-Language: en-US
From:   James Prestwood <prestwoj@gmail.com>
To:     linux-wireless@vger.kernel.org
References: <01c99bfb-b87b-4566-a873-38c6b7dbc0d9@gmail.com>
In-Reply-To: <01c99bfb-b87b-4566-a873-38c6b7dbc0d9@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 10/17/23 7:42 AM, James Prestwood wrote:
> Hi,
> 
> Currently it is not possible to receive multicast action frames (AFAIK) 
> unless EXT_FEATURE_MULTICAST_REGISTRATIONS is supported, which is 
> currently only ath9k (and hwsim). This was added to support DPP which 
> I'm also trying to do on a system using ath10k (potentially ath11k in 
> the future). The original change [1] to ath9k was quite simple and just 
> set FIF_MCAST_ACTION to the list of filters.
> 
> I tried doing this for ath10k with no luck, and looking deeper it 
> appears the firmware API (ATH10K_FW_WMI_OP_VERSION_TLV) doesn't have the 
> "rx_filter" command. I'm using a QCA6174.
> 
> I also noticed the "configure_filter" op for ath10k seems to be monitor 
> specific.
> 
> So I'm wondering if this is something the firmware needs to support (if 
> so I guess I'm SOL unless someone wants to add that). If not I could use 
> some guidance on how I could support it if its possible to modify the 
> ath10k driver.
> 
> Thanks,
> James
> 
> [1] 
> https://lore.kernel.org/linux-wireless/20200426084733.7889-1-jouni@codeaurora.org/

Figured it out, I had misunderstood what "monitor" meant in the context 
of changing an RX filter. Patch sent.

https://lore.kernel.org/linux-wireless/20231017165306.118779-1-prestwoj@gmail.com/T/#u