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

File Facts

System

Linux kernel

Corpus path

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

Extension

.h

Size

1421 bytes

Lines

47

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

• wcn36xx.h

Detected Declarations

• struct ftm_rsp_msg
• struct ftm_payload
• function wcn36xx_tm_cmd

Annotated Snippet

struct ftm_rsp_msg {
	u16 msg_id;
	u16 msg_body_length;
	u32 resp_status;
	u8 msg_response[];
} __packed;

/* The request buffer of FTM which contains a byte of command and the request */
struct ftm_payload {
	u16 ftm_cmd_type;
	struct ftm_rsp_msg ftm_cmd_msg;
} __packed;

#define MSG_GET_BUILD_RELEASE_NUMBER 0x32A2

#ifdef CONFIG_NL80211_TESTMODE
int wcn36xx_tm_cmd(struct ieee80211_hw *hw, struct ieee80211_vif *vif,
		   void *data, int len);

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

#endif

Annotation

• Immediate include surface: `wcn36xx.h`.
• Detected declarations: `struct ftm_rsp_msg`, `struct ftm_payload`, `function wcn36xx_tm_cmd`.
• 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.