drivers/net/wireless/ath/ath9k/dfs.h

File Facts

System

Linux kernel

Corpus path

drivers/net/wireless/ath/ath9k/dfs.h

Extension

.h

Size

1713 bytes

Lines

46

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

• ../dfs_pattern_detector.h

Detected Declarations

• function ath9k_dfs_process_phyerr

Annotated Snippet

#ifndef ATH9K_DFS_H
#define ATH9K_DFS_H
#include "../dfs_pattern_detector.h"

#if defined(CONFIG_ATH9K_DFS_CERTIFIED)
/**
 * ath9k_dfs_process_phyerr - process radar PHY error
 * @sc: ath_softc
 * @data: RX payload data
 * @rs: RX status after processing descriptor
 * @mactime: receive time
 *
 * This function is called whenever the HW DFS module detects a radar
 * pulse and reports it as a PHY error.
 *
 * The radar information provided as raw payload data is validated and
 * filtered for false pulses. Events passing all tests are forwarded to
 * the DFS detector for pattern detection.
 */
void ath9k_dfs_process_phyerr(struct ath_softc *sc, void *data,
			      struct ath_rx_status *rs, u64 mactime);
#else
static inline void
ath9k_dfs_process_phyerr(struct ath_softc *sc, void *data,
			 struct ath_rx_status *rs, u64 mactime) { }
#endif

#endif /* ATH9K_DFS_H */

Annotation

• Immediate include surface: `../dfs_pattern_detector.h`.
• Detected declarations: `function ath9k_dfs_process_phyerr`.
• 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.