drivers/comedi/drivers/tests/comedi_example_test.c

File Facts

System

Linux kernel

Corpus path

drivers/comedi/drivers/tests/comedi_example_test.c

Extension

.c

Size

1769 bytes

Lines

72

Domain

Driver Families

Bucket

drivers/comedi

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
• unittest.h

Detected Declarations

• struct comedi_device
• function init_fake
• function test0
• function unittest_enter
• function unittest_exit
• module init unittest_enter

Annotated Snippet

module_init(unittest_enter);
module_exit(unittest_exit);

MODULE_AUTHOR("Spencer Olson <olsonse@umich.edu>");
MODULE_DESCRIPTION("Comedi unit-tests example");
MODULE_LICENSE("GPL");
/* **** END simple module entry/exit functions **** */

Annotation

• Immediate include surface: `linux/module.h`, `unittest.h`.
• Detected declarations: `struct comedi_device`, `function init_fake`, `function test0`, `function unittest_enter`, `function unittest_exit`, `module init unittest_enter`.
• Atlas domain: Driver Families / drivers/comedi.
• 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.