brcmf_p2p_tx_action_frame(9)

📦 version 7.3.1, in nixpkgs unstable

💅 brcmf_p2p_tx_action_frame — the Kernel API Manual glow-up ✨

okay so bestie, this one lives in the Kernel API Manual and honestly? it's giving "short and iconic." no cap. let's get into it 🎀

🌸 NAME 🌸

brcmf_p2p_tx_action_frame — send action frame over fil.

(that's "fil," not a typo, don't come for me 🫶)

✨ SYNOPSIS ✨

s32 brcmf_p2p_tx_action_frame (struct brcmf_if *ifp , struct
brcmf_p2p_info *p2p , struct brcmf_fil_af_params_le *af_params );

she takes three args and returns an s32, periodt. 💅

🦋 ARGUMENTS 🦋

  • ifp — interface to transmit on. like, which one are we sending from, bestie?
  • p2p — p2p info struct for vif. this is the whole vibe container for the virtual interface.
  • af_params — action frame data/info. all the actual frame tea goes in here. 🍓

🔥 DESCRIPTION 🔥

so the whole point of this function is: send an action frame immediately, with no channel synchronization. not me skipping the channel sync line entirely 💀 — that's literally the design, it does not wait to sync up first.

and here's the important part, the main character detail: this function waits for a completion event before it returns. so it blocks. it does not just yeet the frame and dip.

which event is it waiting on? the WLC_E_ACTION_FRAME_COMPLETE event — that's the one you get when the action frame has actually been transmitted. 🎀 so like, frame goes out → event comes in → function finally returns. slay.

lowkey important: it's a blocking wait on a completion event, so don't act surprised when it takes a sec. that's the deal. 💖

👑 SEE ALSO 👑

okay this section is the whole group chat, no one gets left out. 💜

the kernel file to check:

  • ./drivers/net/wireless/broadcom/brcm80211/brcmfmac/p2p.c

and the whole crew of related pages, all of them:

like I said. everybody. 🌈

💫 and that's the page!! sourced from ./drivers/net/wireless/broadco..., dated October 2026. go send some action frames bestie, you got this 🧚‍♀️✨
📦 where this page comes from