drivers/net/wireless/broadcom/brcm80211/brcmsmac/brcms_trace_events.h

File Facts

System

Linux kernel

Corpus path

drivers/net/wireless/broadcom/brcm80211/brcmsmac/brcms_trace_events.h

Extension

.h

Size

1410 bytes

Lines

41

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.

Dependency Surface

• linux/types.h
• linux/device.h
• linux/tracepoint.h
• mac80211_if.h
• brcms_trace_brcmsmac.h
• brcms_trace_brcmsmac_tx.h
• brcms_trace_brcmsmac_msg.h

Detected Declarations

• function Copyright

Annotated Snippet

#ifndef __BRCMS_TRACE_EVENTS_H
#define __BRCMS_TRACE_EVENTS_H

#include <linux/types.h>
#include <linux/device.h>
#include <linux/tracepoint.h>
#include "mac80211_if.h"

#ifndef CONFIG_BRCM_TRACING
#undef TRACE_EVENT
#define TRACE_EVENT(name, proto, ...) \
static inline void trace_ ## name(proto) {}
#undef DECLARE_EVENT_CLASS
#define DECLARE_EVENT_CLASS(...)
#undef DEFINE_EVENT
#define DEFINE_EVENT(evt_class, name, proto, ...) \
static inline void trace_ ## name(proto) {}
#endif

#include "brcms_trace_brcmsmac.h"
#include "brcms_trace_brcmsmac_tx.h"
#include "brcms_trace_brcmsmac_msg.h"

#endif /* __TRACE_BRCMSMAC_H */

Annotation

• Immediate include surface: `linux/types.h`, `linux/device.h`, `linux/tracepoint.h`, `mac80211_if.h`, `brcms_trace_brcmsmac.h`, `brcms_trace_brcmsmac_tx.h`, `brcms_trace_brcmsmac_msg.h`.
• Detected declarations: `function Copyright`.
• Atlas domain: Driver Families / drivers/net.
• Implementation status: source implementation candidate.

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.