drivers/pps/clients/pps-ldisc.c

File Facts

System

Linux kernel

Corpus path

drivers/pps/clients/pps-ldisc.c

Extension

.c

Size

3245 bytes

Lines

142

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/module.h
• linux/serial_core.h
• linux/tty.h
• linux/pps_kernel.h
• linux/bug.h

Detected Declarations

• function Copyright
• function pps_tty_open
• function pps_tty_close
• function pps_tty_init
• function pps_tty_cleanup
• module init pps_tty_init

Annotated Snippet

module_init(pps_tty_init);
module_exit(pps_tty_cleanup);

MODULE_ALIAS_LDISC(N_PPS);
MODULE_AUTHOR("Rodolfo Giometti <giometti@linux.it>");
MODULE_DESCRIPTION("PPS TTY device driver");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/module.h`, `linux/serial_core.h`, `linux/tty.h`, `linux/pps_kernel.h`, `linux/bug.h`.
• Detected declarations: `function Copyright`, `function pps_tty_open`, `function pps_tty_close`, `function pps_tty_init`, `function pps_tty_cleanup`, `module init pps_tty_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.