drivers/tty/n_null.c

File Facts

System

Linux kernel

Corpus path

drivers/tty/n_null.c

Extension

.c

Size

1026 bytes

Lines

51

Domain

Driver Families

Bucket

drivers/tty

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/types.h
• linux/errno.h
• linux/tty.h
• linux/module.h

Detected Declarations

• function Copyright
• function n_null_write
• function n_null_init
• function n_null_exit
• module init n_null_init

Annotated Snippet

module_init(n_null_init);
module_exit(n_null_exit);

MODULE_LICENSE("GPL");
MODULE_AUTHOR("Alan Cox");
MODULE_ALIAS_LDISC(N_NULL);
MODULE_DESCRIPTION("Null ldisc driver");

Annotation

• Immediate include surface: `linux/types.h`, `linux/errno.h`, `linux/tty.h`, `linux/module.h`.
• Detected declarations: `function Copyright`, `function n_null_write`, `function n_null_init`, `function n_null_exit`, `module init n_null_init`.
• Atlas domain: Driver Families / drivers/tty.
• 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.