brcmf_p2p_afx_handler(9)

🦋 brcmf_p2p_afx_handler ✨

okay so first things first, bestie — this page is brcmf_p2p_afx_handler(9), from the Kernel API Manual. that's the manual name, that's the whole vibe. it's a kernel API page about a worker thread and it is, and i say this with love, extremely short. let's get into it 💅

---

💖 NAME 💖

brcmf_p2p_afx_handler — afx worker thread.

that's it. that's the name section. it's giving minimalist icon behavior and honestly? respect. 🎀

---

✨ SYNOPSIS ✨

void brcmf_p2p_afx_handler (struct work_struct *work );

so she's a void function, no return value, takes one pointer to a struct work_struct called work, and then just... does her thing. note the space before the closing paren — that's exactly how it's written on the page, and we do not touch it, no cap 🫶

---

🌸 ARGUMENTS 🌸

• work — this is it. this is the whole entry. the page lists work and then just kinda ✨leaves✨. no description, no elaboration, nothing. i'm not gonna make up lore for it because that would be lying to you and we don't do that here 😭 what i can tell you is that it's a struct work_struct *, which is right there in the synopsis, and that's literally every crumb this manpage gives us. iconic of her to be so mysterious tbh 🙈

---

🔥 SEE ALSO 🔥

okay this is the part where she suddenly has SO much to say. the whole crew, in the order the page lists them:

• Kernel file ./drivers/net/wireless/broadcom/brcm80211/brcmfmac/p2p.c
• struct brcmf_p2p_disc_st_le(9)
• enum brcmf_p2p_disc_state(9)
• struct brcmf_p2p_scan_le(9)
• struct brcmf_p2p_pub_act_frame(9)
• struct brcmf_p2p_action_frame(9)
• struct brcmf_p2psd_gas_pub_act_frame(9)
• struct brcmf_config_af_params(9)
• brcmf_p2p_is_pub_action(9)
• brcmf_p2p_is_dpp_pub_action(9)
• brcmf_p2p_is_p2p_action(9)
• brcmf_p2p_is_gas_action(9)
• brcmf_p2p_print_actframe(9)
• brcmf_p2p_set_firmware(9)
• brcmf_p2p_generate_bss_mac(9)
• brcmf_p2p_scan_is_p2p_request(9)
• brcmf_p2p_set_discover_state(9)
• brcmf_p2p_deinit_discovery(9)
• brcmf_p2p_enable_discovery(9)
• brcmf_p2p_escan(9)
• brcmf_p2p_run_escan(9)
• brcmf_p2p_find_listen_channel(9)
• brcmf_p2p_scan_prep(9)
• brcmf_p2p_discover_listen(9)
• brcmf_p2p_remain_on_channel(9)
• brcmf_p2p_notify_listen_complete(9)
• brcmf_p2p_cancel_remain_on_channel(9)
• brcmf_p2p_act_frm_search(9)
• brcmf_p2p_af_searching_channel(9)
• brcmf_p2p_scan_finding_common_channel(9)
• brcmf_p2p_abort_action_frame(9)
• brcmf_p2p_stop_wait_next_action_frame(9)
• brcmf_p2p_gon_req_collision(9)
• brcmf_p2p_notify_action_frame_rx(9)
• brcmf_p2p_notify_action_tx_complete(9)
• brcmf_p2p_tx_action_frame(9)
• brcmf_p2p_pub_af_tx(9)
• brcmf_p2p_send_action_frame(9)
• brcmf_p2p_notify_rx_mgmt_p2p_probereq(9)
• brcmf_p2p_get_current_chanspec(9)
• brcmf_p2p_ifchange(9)
• brcmf_p2p_create_p2pdev(9)
• brcmf_p2p_add_vif(9)
• brcmf_p2p_del_vif(9)
• brcmf_p2p_attach(9)
• brcmf_p2p_detach(9)

like, 46 references and one (1) undocumented argument. the imbalance is lowkey sending me 💀 but she ate, she ate fr fr 👑

little heads-up bestie: every one of these is written exactly as it appears on the page — the (9) suffixes, the struct/enum prefixes, all of it. don't go "fixing" the naming when you look them up, ok? 🍓

---

---

and that's the whole page!! a worker thread, an argument called work with zero description, and a see-also list longer than my screen. main character energy honestly 🌈

cute lil sign-off: this page comes from the source path ./drivers/net/wireless/broadco... (yes, that's how it's printed on the page — cut off mid-path, we don't edit the source line), dated October 2026, and the title footer repeats brcmf_p2p_afx_handler(9) 🧚💜

go touch some struct work_struct, bestie. ily. 💖