drivers/greybus/debugfs.c
Source file repositories/reference/linux-study-clean/drivers/greybus/debugfs.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/greybus/debugfs.c- Extension
.c- Size
- 515 bytes
- Lines
- 30
- Domain
- Driver Families
- Bucket
- drivers/greybus
- 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/debugfs.hlinux/greybus.h
Detected Declarations
function gb_debugfs_initfunction gb_debugfs_cleanupexport gb_debugfs_get
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
/*
* Greybus debugfs code
*
* Copyright 2014 Google Inc.
* Copyright 2014 Linaro Ltd.
*/
#include <linux/debugfs.h>
#include <linux/greybus.h>
static struct dentry *gb_debug_root;
void __init gb_debugfs_init(void)
{
gb_debug_root = debugfs_create_dir("greybus", NULL);
}
void gb_debugfs_cleanup(void)
{
debugfs_remove_recursive(gb_debug_root);
gb_debug_root = NULL;
}
struct dentry *gb_debugfs_get(void)
{
return gb_debug_root;
}
EXPORT_SYMBOL_GPL(gb_debugfs_get);
Annotation
- Immediate include surface: `linux/debugfs.h`, `linux/greybus.h`.
- Detected declarations: `function gb_debugfs_init`, `function gb_debugfs_cleanup`, `export gb_debugfs_get`.
- Atlas domain: Driver Families / drivers/greybus.
- 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.