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

File Facts

System

Linux kernel

Corpus path

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

Extension

.c

Size

606 bytes

Lines

24

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

• debug.h

Detected Declarations

• function qtnf_debugfs_init
• function qtnf_debugfs_remove
• function qtnf_debugfs_add_entry

Annotated Snippet

// SPDX-License-Identifier: GPL-2.0+
/* Copyright (c) 2015-2016 Quantenna Communications. All rights reserved. */

#include "debug.h"

void qtnf_debugfs_init(struct qtnf_bus *bus, const char *name)
{
	struct dentry *parent = qtnf_get_debugfs_dir();

	bus->dbg_dir = debugfs_create_dir(name, parent);
}

void qtnf_debugfs_remove(struct qtnf_bus *bus)
{
	debugfs_remove_recursive(bus->dbg_dir);
	bus->dbg_dir = NULL;
}

void qtnf_debugfs_add_entry(struct qtnf_bus *bus, const char *name,
			    int (*fn)(struct seq_file *seq, void *data))
{
	debugfs_create_devm_seqfile(bus->dev, name, bus->dbg_dir, fn);
}

Annotation

• Immediate include surface: `debug.h`.
• Detected declarations: `function qtnf_debugfs_init`, `function qtnf_debugfs_remove`, `function qtnf_debugfs_add_entry`.
• 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.