drivers/net/wireless/broadcom/brcm80211/brcmfmac/fweh.h
Source file repositories/reference/linux-study-clean/drivers/net/wireless/broadcom/brcm80211/brcmfmac/fweh.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/net/wireless/broadcom/brcm80211/brcmfmac/fweh.h- Extension
.h- Size
- 12082 bytes
- Lines
- 402
- Domain
- Driver Families
- Bucket
- drivers/net
- Inferred role
- Driver Families: implementation source
- Status
- source implementation candidate
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Touches IRQ or DMA behavior; this matters for the representative real-device path.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/unaligned.hlinux/skbuff.hlinux/if_ether.hlinux/if.h
Detected Declarations
struct brcmf_pubstruct brcmf_ifstruct brcmf_cfg80211_infostruct brcm_ethhdrstruct brcmf_event_msg_bestruct brcmf_eventstruct brcmf_event_msgstruct brcmf_if_eventstruct brcmf_fweh_event_map_itemstruct brcmf_fweh_event_mapstruct brcmf_fweh_infoenum brcmf_fweh_event_codefunction brcmf_fweh_process_skb
Annotated Snippet
struct brcm_ethhdr {
__be16 subtype;
__be16 length;
u8 version;
u8 oui[3];
__be16 usr_subtype;
} __packed;
struct brcmf_event_msg_be {
__be16 version;
__be16 flags;
__be32 event_type;
__be32 status;
__be32 reason;
__be32 auth_type;
__be32 datalen;
u8 addr[ETH_ALEN];
char ifname[IFNAMSIZ];
u8 ifidx;
u8 bsscfgidx;
} __packed;
/**
* struct brcmf_event - contents of broadcom event packet.
*
* @eth: standard ether header.
* @hdr: broadcom specific ether header.
* @msg: common part of the actual event message.
*/
struct brcmf_event {
struct ethhdr eth;
struct brcm_ethhdr hdr;
struct brcmf_event_msg_be msg;
} __packed;
/**
* struct brcmf_event_msg - firmware event message.
*
* @version: version information.
* @flags: event flags.
* @event_code: firmware event code.
* @status: status information.
* @reason: reason code.
* @auth_type: authentication type.
* @datalen: length of event data buffer.
* @addr: ether address.
* @ifname: interface name.
* @ifidx: interface index.
* @bsscfgidx: bsscfg index.
*/
struct brcmf_event_msg {
u16 version;
u16 flags;
u32 event_code;
u32 status;
u32 reason;
s32 auth_type;
u32 datalen;
u8 addr[ETH_ALEN];
char ifname[IFNAMSIZ];
u8 ifidx;
u8 bsscfgidx;
};
struct brcmf_if_event {
u8 ifidx;
u8 action;
u8 flags;
u8 bsscfgidx;
u8 role;
};
typedef int (*brcmf_fweh_handler_t)(struct brcmf_if *ifp,
const struct brcmf_event_msg *evtmsg,
void *data);
/**
* struct brcmf_fweh_event_map_item - fweh event and firmware event pair.
*
* @code: fweh event code as used by higher layers.
* @fwevt_code: firmware event code as used by firmware.
*
* This mapping is needed when a functionally identical event has a
* different numerical definition between vendors. When such mapping
* is needed the higher layer event code should not collide with the
* firmware event.
*/
struct brcmf_fweh_event_map_item {
enum brcmf_fweh_event_code code;
u32 fwevt_code;
Annotation
- Immediate include surface: `linux/unaligned.h`, `linux/skbuff.h`, `linux/if_ether.h`, `linux/if.h`.
- Detected declarations: `struct brcmf_pub`, `struct brcmf_if`, `struct brcmf_cfg80211_info`, `struct brcm_ethhdr`, `struct brcmf_event_msg_be`, `struct brcmf_event`, `struct brcmf_event_msg`, `struct brcmf_if_event`, `struct brcmf_fweh_event_map_item`, `struct brcmf_fweh_event_map`.
- Atlas domain: Driver Families / drivers/net.
- Implementation status: source implementation candidate.
- IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.