brcmf_btcoex_attach(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– brcmf_btcoex_attach(9) β€” like, the Kernel API Manual page, bestie πŸ’–

okay so picture this: you're deep in the kernel source, the brcmfmac driver, and you need the Bluetooth-coexistence data to actually exist before anything else can happen. That's this function. It's the "get set up first" girlie. And yes, we're in section 9 of the Kernel API Manual β€” the grown-up kernel-docs section. Iykyk. ✨


🌸 NAME 🌸

brcmf_btcoex_attach β€” initialize BT coex data. That's it, that's the whole job. She shows up, she initializes the BT coex data. Main character energy, zero drama. πŸ’…


✨ SYNOPSIS ✨

int brcmf_btcoex_attach (struct brcmf_cfg80211_info *cfg );

(no cap, that's the exact signature β€” space before the closing paren and all, copy it character for character bestie 🫢)


πŸŽ€ ARGUMENTS πŸŽ€

  • cfg β€” the driver's private cfg80211 data. Yeah. That's the one whole argument. She takes exactly one thing and she's not sorry.

πŸ¦‹ RETURN πŸ¦‹

Returns 0 on success. That's the entire return story. 0 = we ate. πŸ”₯


πŸ‘‘ SEE ALSO πŸ‘‘

The kernel file for this one lives at:

./drivers/net/wireless/broadcom/brcm80211/brcmfmac/btcoex.c

and honestly? Go read the whole btcoex friend group, they're all linked here:


πŸ’€ reminder: the source line in the footer is literally truncated in the page as ./drivers/net/wireless/broadco... β€” that's not me being lazy, that's just how it's printed. Also this page is dated October 2026, so yes, she's from the future.

okay that's the page!! signing off from the Kernel API Manual, source file ./drivers/net/wireless/broadco... (cut off exactly like that, don't come for me), dated October 2026, under the title brcmf_btcoex_attach(9). Slay, go init your coex data. πŸ§šβ­πŸ’œ

πŸ“¦ where this page comes from