drivers/net/wireless/ath/ath12k/testmode.h

File Facts

System

Linux kernel

Corpus path

drivers/net/wireless/ath/ath12k/testmode.h

Extension

.h

Size

1022 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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• core.h
• hif.h

Detected Declarations

• function ath12k_tm_wmi_event_unsegmented

Annotated Snippet

#include "core.h"
#include "hif.h"

#ifdef CONFIG_NL80211_TESTMODE

void ath12k_tm_wmi_event_unsegmented(struct ath12k_base *ab, u32 cmd_id,
				     struct sk_buff *skb);
void ath12k_tm_process_event(struct ath12k_base *ab, u32 cmd_id,
			     const struct ath12k_wmi_ftm_event *ftm_msg,
			     u16 length);
int ath12k_tm_cmd(struct ieee80211_hw *hw, struct ieee80211_vif *vif,
		  void *data, int len);

#else

static inline void ath12k_tm_wmi_event_unsegmented(struct ath12k_base *ab, u32 cmd_id,
						   struct sk_buff *skb)
{
}

static inline void ath12k_tm_process_event(struct ath12k_base *ab, u32 cmd_id,
					   const struct ath12k_wmi_ftm_event *msg,
					   u16 length)
{
}

static inline int ath12k_tm_cmd(struct ieee80211_hw *hw,
				struct ieee80211_vif *vif,
				void *data, int len)
{
	return 0;
}

#endif

Annotation

• Immediate include surface: `core.h`, `hif.h`.
• Detected declarations: `function ath12k_tm_wmi_event_unsegmented`.
• 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.