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

File Facts

System

Linux kernel

Corpus path

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

Extension

.h

Size

853 bytes

Lines

38

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/debugfs.h
• core.h
• bus.h

Detected Declarations

• function qtnf_debugfs_init

Annotated Snippet

#ifndef _QTN_FMAC_DEBUG_H_
#define _QTN_FMAC_DEBUG_H_

#include <linux/debugfs.h>

#include "core.h"
#include "bus.h"

#ifdef CONFIG_DEBUG_FS

void qtnf_debugfs_init(struct qtnf_bus *bus, const char *name);
void qtnf_debugfs_remove(struct qtnf_bus *bus);
void qtnf_debugfs_add_entry(struct qtnf_bus *bus, const char *name,
			    int (*fn)(struct seq_file *seq, void *data));

#else

static inline void qtnf_debugfs_init(struct qtnf_bus *bus, const char *name)
{
}

static inline void qtnf_debugfs_remove(struct qtnf_bus *bus)
{
}

static inline void
qtnf_debugfs_add_entry(struct qtnf_bus *bus, const char *name,
		       int (*fn)(struct seq_file *seq, void *data))
{
}

#endif /* CONFIG_DEBUG_FS */

#endif /* _QTN_FMAC_DEBUG_H_ */

Annotation

• Immediate include surface: `linux/debugfs.h`, `core.h`, `bus.h`.
• Detected declarations: `function qtnf_debugfs_init`.
• 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.