drivers/acpi/debugfs.c

File Facts

System

Linux kernel

Corpus path

drivers/acpi/debugfs.c

Extension

.c

Size

391 bytes

Lines

20

Domain

Driver Families

Bucket

drivers/acpi

Inferred role

Driver Families: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/export.h
• linux/init.h
• linux/debugfs.h
• linux/acpi.h
• internal.h

Detected Declarations

• function acpi_debugfs_init
• export acpi_debugfs_dir

Annotated Snippet

// SPDX-License-Identifier: GPL-2.0-only
/*
 * debugfs.c - ACPI debugfs interface to userspace.
 */

#include <linux/export.h>
#include <linux/init.h>
#include <linux/debugfs.h>
#include <linux/acpi.h>

#include "internal.h"

struct dentry *acpi_debugfs_dir;
EXPORT_SYMBOL_GPL(acpi_debugfs_dir);

void __init acpi_debugfs_init(void)
{
	acpi_debugfs_dir = debugfs_create_dir("acpi", NULL);
}

Annotation

• Immediate include surface: `linux/export.h`, `linux/init.h`, `linux/debugfs.h`, `linux/acpi.h`, `internal.h`.
• Detected declarations: `function acpi_debugfs_init`, `export acpi_debugfs_dir`.
• Atlas domain: Driver Families / drivers/acpi.
• Implementation status: integration 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.