drivers/net/wireless/quantenna/qtnfmac/shm_ipc_defs.h

File Facts

System

Linux kernel

Corpus path

drivers/net/wireless/quantenna/qtnfmac/shm_ipc_defs.h

Extension

.h

Size

807 bytes

Lines

34

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

• linux/types.h

Detected Declarations

• struct qtnf_shm_ipc_region_header
• struct qtnf_shm_ipc_region
• enum qtnf_shm_ipc_region_flags

Annotated Snippet

struct qtnf_shm_ipc_region_header {
	__le32 flags;
	__le16 data_len;
} __packed;

union qtnf_shm_ipc_region_headroom {
	struct qtnf_shm_ipc_region_header hdr;
	u8 headroom[QTN_IPC_REG_HDR_SZ];
} __packed;

struct qtnf_shm_ipc_region {
	union qtnf_shm_ipc_region_headroom headroom;
	u8 data[QTN_IPC_MAX_DATA_SZ];
} __packed;

#endif /* _QTN_FMAC_SHM_IPC_DEFS_H_ */

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct qtnf_shm_ipc_region_header`, `struct qtnf_shm_ipc_region`, `enum qtnf_shm_ipc_region_flags`.
• 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.