drivers/hwtracing/stm/ftrace.c

File Facts

System

Linux kernel

Corpus path

drivers/hwtracing/stm/ftrace.c

Extension

.c

Size

2247 bytes

Lines

88

Domain

Driver Families

Bucket

drivers/hwtracing

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/module.h
• linux/stm.h
• linux/trace.h

Detected Declarations

• function stm_ftrace_write
• function stm_ftrace_link
• function stm_ftrace_unlink
• function stm_ftrace_init
• function stm_ftrace_exit
• module init stm_ftrace_init

Annotated Snippet

module_init(stm_ftrace_init);
module_exit(stm_ftrace_exit);

MODULE_LICENSE("GPL v2");
MODULE_DESCRIPTION("stm_ftrace driver");
MODULE_AUTHOR("Chunyan Zhang <zhang.chunyan@linaro.org>");

Annotation

• Immediate include surface: `linux/module.h`, `linux/stm.h`, `linux/trace.h`.
• Detected declarations: `function stm_ftrace_write`, `function stm_ftrace_link`, `function stm_ftrace_unlink`, `function stm_ftrace_init`, `function stm_ftrace_exit`, `module init stm_ftrace_init`.
• Atlas domain: Driver Families / drivers/hwtracing.
• 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.