drivers/tty/serial/8250/8250_parisc.c

File Facts

System

Linux kernel

Corpus path

drivers/tty/serial/8250/8250_parisc.c

Extension

.c

Size

3899 bytes

Lines

132

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/errno.h
• linux/init.h
• linux/interrupt.h
• linux/ioport.h
• linux/module.h
• linux/serial_core.h
• linux/signal.h
• linux/types.h
• asm/hardware.h
• asm/parisc-device.h
• asm/io.h
• 8250.h

Detected Declarations

• function serial_init_chip
• function probe_serial_gsc
• module init probe_serial_gsc

Annotated Snippet

module_init(probe_serial_gsc);

MODULE_DESCRIPTION("Serial Device Initialisation for Lasi/Asp/Wax/Dino");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/errno.h`, `linux/init.h`, `linux/interrupt.h`, `linux/ioport.h`, `linux/module.h`, `linux/serial_core.h`, `linux/signal.h`, `linux/types.h`.
• Detected declarations: `function serial_init_chip`, `function probe_serial_gsc`, `module init probe_serial_gsc`.
• 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.