STRUCT BRCMF_FWEH_EVENT_MAP_ITEM(9)

💖 struct brcmf_fweh_event_map_item(9) 💖

okay so bestie, welcome to the Kernel API Manual ✨ — this is the page for struct brcmf_fweh_event_map_item, and honestly? it's a little matchmaker struct. it pairs up two event codes so they can find each other. 🫶

---

🌸 NAME 🌸

struct brcmf_fweh_event_map_item — the fweh event and firmware event pair. like, a buddy system but for codes. 💅

---

✨ SYNOPSIS ✨

struct brcmf_fweh_event_map_item {
    enum brcmf_fweh_event_code code;
    u32 fwevt_code;
 };

look at her. two fields. no notes. 🌈

---

🎀 Members 🎀

• code — the fweh event code, aka the one the higher layers actually use. this is the code with main character energy 👑
• fwevt_code — the firmware event code, aka the one the firmware uses. same vibe, different number, iykyk 💀

---

🦋 Description 🦋

so here's the tea, bestie 🍓: sometimes a functionally identical event has a different numerical definition between vendors. like, same event, different digits. tragic. truly. 😭

that's exactly when this mapping is needed — it's the translator, the go-between, the friend who knows both friend groups. 🧚

⚠️ important caveat incoming: when such mapping is needed, the higher layer event code should not collide with the firmware event. no overlapping numbers, no drama, periodt. 🔥

---

⭐ SEE ALSO ⭐

• Kernel file ./drivers/net/wireless/broadcom/brcm80211/brcmfmac/fweh.h 💜
• struct brcm_ethhdr(9)
• struct brcmf_event(9)
• struct brcmf_event_msg(9)
• struct brcmf_fweh_event_map(9)
• struct brcmf_fweh_info(9)

go read those too, they're all iconic in their own way 🌸

---

and that's the page!! 🎀 ngl this one was short and sweet. shoutout to the source ./drivers/net/wireless/broadco... and the date October 2026 — mwah, slayed, no cap 💅✨🦋