mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Allen Ye (葉芷勳)" <Allen.Ye@mediatek.com>
To: "pooventhiran.g@oss.qualcomm.com" <pooventhiran.g@oss.qualcomm.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"johannes@sipsolutions.net" <johannes@sipsolutions.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"jouni.malinen@oss.qualcomm.com" <jouni.malinen@oss.qualcomm.com>,
	"asathish@qti.qualcomm.com" <asathish@qti.qualcomm.com>
Subject: Re: [PATCH wireless-next v4 08/21] wifi: nl80211/cfg80211: pack SMD dynamic context along with frame
Date: Mon, 16 Nov 2026 03:38:29 +0000	[thread overview]
Message-ID: <9ab4068ed0dec1f9a13a2ba399119df04478d96a.camel@mediatek.com> (raw)
In-Reply-To: <a509d2e4-c192-443f-a6b8-587efca47ffd@oss.qualcomm.com>

On Fri, 2026-11-13 at 23:49 +0530, Pooventhiran G wrote:
> 
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
> 
> 
> On 11/11/2026 02:44 pm, Allen Ye wrote:
> > On Fri, 2026-11-06 at 13:28 +0530, Pooventhiran G wrote:
> > 
> > Hi Pooventhiran,
> > 
> > A question on how the context is collected here.
> > 
> > > While packing the received management frame in
> > > nl80211_send_mgmt() to
> > > send to userspace, nest the SMD dynamic context along with the
> > > frame
> > > message.
> > 
> > On MediaTek chipsets (mt76), the dynamic context is kept in FW/HW,
> > so
> > the driver has to fetch it from the firmware with an MCU command.
> > This
> > means the driver has to hold the ST request frame until the
> > firmware
> > replies with an event, and only then pass the frame up. Holding RX
> > frames in the driver is the problematic part: the frame has to be
> > kept
> > outside the normal RX path, kept in order with the frames that
> > follow
> > it, and handled if the firmware reply is delayed or never arrives.
> > 
> > 1. With the context attached to the frame, how it gets collected
> > depends on each vendor driver's own implementation (on mt76, this
> > may
> > mean holding the frame in the driver as described above). If
> > userspace
> > instead queried it via GET_SMD_CTX / SMD_CTX_EVENT for ST
> > preparation
> > and ST execution via the current AP MLD, as it already does for ST
> > execution via the target AP MLD, the flow would be the same for
> > every
> > driver, regardless of where the context is kept. Would that be
> > acceptable?
> > 
> > 2. If not, could the frame-attached context be optional (e.g.
> > behind a
> > capability flag), with userspace falling back to GET_SMD_CTX?
> > 
> 
> Hi Allen. Sure, that option could also be added if some drivers
> choose not to
> pack in the rx_mgmt frame itself. Since it will be a fallback, I can
> change
> hostapd to directly query the driver for context using GET_SMD_CTX if
> it does
> not find the context attached to the received frame?
> 

Hi Pooventhiran,
That sounds good to put the logic in hostapd.

Thanks,
Allen

> > Thanks,
> > Allen
> 


  reply	other threads:[~2026-11-16  3:38 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06  7:58 [PATCH wireless-next v4 00/21] wifi: Add Seamless Mobility Domain (SMD) AP support Pooventhiran G
2026-11-06  7:58 ` [PATCH wireless-next v4 01/21] wifi: nl80211: define Seamless Mobility Domain (SMD) device capability Pooventhiran G
2026-11-10 14:15   ` Johannes Berg
2026-11-10 14:26     ` Johannes Berg
2026-11-13 15:23       ` Pooventhiran G
2026-11-06  7:58 ` [PATCH wireless-next v4 02/21] wifi: nl80211/cfg80211: define interfaces for SMD setup and STA update Pooventhiran G
2026-11-10 18:18   ` Johannes Berg
2026-11-06  7:58 ` [PATCH wireless-next v4 03/21] wifi: nl80211: add SMD BSS Transition sub-state STA flags Pooventhiran G
2026-11-10 18:27   ` Johannes Berg
2026-11-06  7:58 ` [PATCH wireless-next v4 04/21] wifi: cfg80211: define layouts for SMD BSS Transition context Pooventhiran G
2026-11-10 18:39   ` Johannes Berg
2026-11-13 18:15     ` Pooventhiran G
2026-11-06  7:58 ` [PATCH wireless-next v4 05/21] wifi: nl80211: define interfaces for SMD BSS Transition context transfer Pooventhiran G
2026-11-10 18:45   ` Johannes Berg
2026-11-13 16:45     ` Pooventhiran G
2026-11-06  7:58 ` [PATCH wireless-next v4 06/21] wifi: ieee80211: define APIs for UHR Link Reconfiguration frame checks Pooventhiran G
2026-11-06  7:58 ` [PATCH wireless-next v4 07/21] wifi: ieee80211: define API to check if frame is class 3 Pooventhiran G
2026-11-06  7:58 ` [PATCH wireless-next v4 08/21] wifi: nl80211/cfg80211: pack SMD dynamic context along with frame Pooventhiran G
2026-11-10 18:51   ` Johannes Berg
2026-11-13 18:17     ` Pooventhiran G
2026-11-11  9:14   ` Allen Ye
2026-11-13 18:19     ` Pooventhiran G
2026-11-16  3:38       ` Allen Ye (葉芷勳) [this message]
2026-11-06  7:58 ` [PATCH wireless-next v4 09/21] wifi: nl80211/cfg80211: add support for SMD context programming Pooventhiran G
2026-11-10 18:55   ` Johannes Berg
2026-11-13 17:54     ` Pooventhiran G
2026-11-06  7:58 ` [PATCH wireless-next v4 10/21] wifi: nl80211/cfg80211: add support for querying SMD context for target AP MLD Pooventhiran G
2026-11-10 19:00   ` Johannes Berg
2026-11-13 18:33     ` Pooventhiran G
2026-11-06  7:58 ` [PATCH wireless-next v4 11/21] wifi: nl80211/cfg80211: define API to notify SMD Drain completion Pooventhiran G
2026-11-10 19:01   ` Johannes Berg
2026-11-13 18:38     ` Pooventhiran G
2026-11-06  7:58 ` [PATCH wireless-next v4 12/21] wifi: mac80211: set SMD parameters for AP setup and STA update Pooventhiran G
2026-11-06  7:58 ` [PATCH wireless-next v4 13/21] wifi: mac80211: apply SMD BSS Transition STA sub-states Pooventhiran G
2026-11-10 20:29   ` Johannes Berg
2026-11-13 18:46     ` Pooventhiran G
2026-11-06  7:58 ` [PATCH wireless-next v4 14/21] wifi: mac80211: add driver_op for SMD substate changes Pooventhiran G
2026-11-10 20:38   ` Johannes Berg
2026-11-13 19:20     ` Pooventhiran G
2026-11-06  7:58 ` [PATCH wireless-next v4 15/21] wifi: mac80211: filter uplink and downlink frames based on SMD states Pooventhiran G
2026-11-06  7:58 ` [PATCH wireless-next v4 16/21] wifi: mac80211: send BlockAck policy in AMPDU action Pooventhiran G
2026-11-10 20:43   ` Johannes Berg
2026-11-06  7:58 ` [PATCH wireless-next v4 17/21] wifi: mac80211: pass rx_data directly from ieee80211_rx_list() Pooventhiran G
2026-11-06  7:58 ` [PATCH wireless-next v4 18/21] wifi: mac80211: handle UHR Link Reconfiguration frame Pooventhiran G
2026-11-06  7:58 ` [PATCH wireless-next v4 19/21] wifi: mac80211: add mac80211 support to handle NL80211_CMD_SET_SMD_CTX Pooventhiran G
2026-11-06  7:58 ` [PATCH wireless-next v4 20/21] wifi: mac80211: add mac80211 support to handle NL80211_CMD_GET_SMD_CTX Pooventhiran G
2026-11-10 20:47   ` Johannes Berg
2026-11-13 19:22     ` Pooventhiran G
2026-11-06  7:58 ` [PATCH wireless-next v4 21/21] wifi: mac80211: define API to invoke SMD Drain Completion event Pooventhiran G
2026-11-10 20:49   ` Johannes Berg
2026-11-13 19:24     ` Pooventhiran G

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=9ab4068ed0dec1f9a13a2ba399119df04478d96a.camel@mediatek.com \
    --to=allen.ye@mediatek.com \
    --cc=asathish@qti.qualcomm.com \
    --cc=johannes@sipsolutions.net \
    --cc=jouni.malinen@oss.qualcomm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pooventhiran.g@oss.qualcomm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®