brcmf_fweh_p2pdev_setup(9)

✨ brcmf_fweh_p2pdev_setup(9) ✨

okay so bestie, buckle up 💖 this is a page straight out of the Kernel API Manual and it's short but it's iconic. We're talking about brcmf_fweh_p2pdev_setup — the little function that tells the firmware event handler whether a P2P device setup is currently going on or has wrapped up. Lowkey one job, but it does it slayfully. 💅

---

🎀 NAME 🎀

brcmf_fweh_p2pdev_setup — P2P device setup ongoing (or not). fr fr that's the whole vibe check: is the setup happening or not. 🦋

---

🌸 SYNOPSIS 🌸

void brcmf_fweh_p2pdev_setup (struct brcmf_if *ifp , bool ongoing );

no cap, that's the whole signature. void return, two args, in and out. 🫶

---

💜 ARGUMENTS 💜

• ifp — the struct brcmf_if on which the setup is taking place or is finished. it's giving "the interface in question," the main character of this whole call. 👑
• ongoing — a bool, and it's literally answering the question "p2p device setup in progress (or not)". true-ish vibes = still going; not = done. ✨

---

🔥 SEE ALSO 🔥

kmuch, here's the whole friend group 🫶 — go read these next:

• Kernel file ./drivers/net/wireless/broadcom/brcm80211/brcmfmac/fweh.c
• struct brcmf_fweh_queue_item(9)
• brcmf_fweh_event_name(9)
• brcmf_fweh_queue_event(9)
• brcmf_fweh_handle_if_event(9)
• brcmf_fweh_dequeue_event(9)
• brcmf_fweh_event_worker(9)
• brcmf_fweh_attach(9)
• brcmf_fweh_detach(9)
• brcmf_fweh_register(9)
• brcmf_fweh_unregister(9)
• brcmf_fweh_activate_events(9)
• brcmf_fweh_process_event(9)

---

💀 real talk though: this is kernel API territory, so don't go calling it from userspace and expecting a cute result. it's for the brcmfmac driver internals, periodt.

---

and that's the page!! 🌈 source/version situation is ./drivers/net/wireless/broadco... and it's dated October 2026 — so yeah, mark your calendars bestie, this manual page is from the future and it ate. 🍓🧚⭐