samples/coresight/coresight-cfg-sample.c

Source file repositories/reference/linux-study-clean/samples/coresight/coresight-cfg-sample.c

File Facts

System: Linux kernel
Corpus path: samples/coresight/coresight-cfg-sample.c
Extension: .c
Size: 1884 bytes
Lines: 74
Domain: Support Tooling And Documentation
Bucket: samples
Inferred role: Support Tooling And Documentation: exported/initcall integration point
Status: integration implementation candidate

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
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

coresight-config.h
coresight-syscfg.h

Detected Declarations

function cscfg_sample_init
function cscfg_sample_exit
module init cscfg_sample_init

Annotated Snippet

module_init(cscfg_sample_init);
module_exit(cscfg_sample_exit);

MODULE_LICENSE("GPL v2");
MODULE_AUTHOR("Mike Leach <mike.leach@linaro.org>");
MODULE_DESCRIPTION("CoreSight Syscfg Example");

Annotation

Immediate include surface: `coresight-config.h`, `coresight-syscfg.h`.
Detected declarations: `function cscfg_sample_init`, `function cscfg_sample_exit`, `module init cscfg_sample_init`.
Atlas domain: Support Tooling And Documentation / samples.
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.