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

File Facts

System

Linux kernel

Corpus path

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

Extension

.h

Size

959 bytes

Lines

39

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

• No C-style include directives detected by the generator.

Detected Declarations

• enum ath12k_fw_ie_type
• enum ath12k_fw_features

Annotated Snippet

#ifndef ATH12K_FW_H
#define ATH12K_FW_H

#define ATH12K_FW_API2_FILE		"firmware-2.bin"
#define ATH12K_FIRMWARE_MAGIC		"QCOM-ATH12K-FW"

enum ath12k_fw_ie_type {
	ATH12K_FW_IE_TIMESTAMP = 0,
	ATH12K_FW_IE_FEATURES = 1,
	ATH12K_FW_IE_AMSS_IMAGE = 2,
	ATH12K_FW_IE_M3_IMAGE = 3,
	ATH12K_FW_IE_AMSS_DUALMAC_IMAGE = 4,
	ATH12K_FW_IE_AUX_UC_IMAGE = 5,
};

enum ath12k_fw_features {
	/* The firmware supports setting the QRTR id via register
	 * PCIE_LOCAL_REG_QRTR_NODE_ID
	 */
	ATH12K_FW_FEATURE_MULTI_QRTR_ID = 0,

	/* The firmware supports MLO capability */
	ATH12K_FW_FEATURE_MLO,

	/* keep last */
	ATH12K_FW_FEATURE_COUNT,
};

void ath12k_fw_map(struct ath12k_base *ab);
void ath12k_fw_unmap(struct ath12k_base *ab);
bool ath12k_fw_feature_supported(struct ath12k_base *ab, enum ath12k_fw_features feat);

#endif /* ATH12K_FW_H */

Annotation

• Detected declarations: `enum ath12k_fw_ie_type`, `enum ath12k_fw_features`.
• 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.