drivers/pps/clients/pps-ktimer.c

File Facts

System

Linux kernel

Corpus path

drivers/pps/clients/pps-ktimer.c

Extension

.c

Size

1749 bytes

Lines

88

Domain

Driver Families

Bucket

drivers/pps

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/kernel.h
• linux/module.h
• linux/init.h
• linux/time.h
• linux/timer.h
• linux/pps_kernel.h

Detected Declarations

• function pps_ktimer_event
• function pps_ktimer_exit
• function pps_ktimer_init
• module init pps_ktimer_init

Annotated Snippet

module_init(pps_ktimer_init);
module_exit(pps_ktimer_exit);

MODULE_AUTHOR("Rodolfo Giometti <giometti@linux.it>");
MODULE_DESCRIPTION("dummy PPS source by using a kernel timer (just for debug)");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/init.h`, `linux/time.h`, `linux/timer.h`, `linux/pps_kernel.h`.
• Detected declarations: `function pps_ktimer_event`, `function pps_ktimer_exit`, `function pps_ktimer_init`, `module init pps_ktimer_init`.
• Atlas domain: Driver Families / drivers/pps.
• 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.