drivers/tty/serial/vt8500_serial.c

File Facts

System

Linux kernel

Corpus path

drivers/tty/serial/vt8500_serial.c

Extension

.c

Size

18039 bytes

Lines

720

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.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/hrtimer.h
• linux/delay.h
• linux/io.h
• linux/ioport.h
• linux/irq.h
• linux/init.h
• linux/console.h
• linux/platform_device.h
• linux/tty.h
• linux/tty_flip.h
• linux/serial_core.h
• linux/serial.h
• linux/slab.h
• linux/clk.h
• linux/of.h
• linux/err.h

Detected Declarations

• struct vt8500_port
• function vt8500_write
• function vt8500_read
• function vt8500_stop_tx
• function vt8500_stop_rx
• function vt8500_enable_ms
• function handle_rx
• function vt8500_tx_empty
• function handle_tx
• function vt8500_start_tx
• function handle_delta_cts
• function vt8500_irq
• function vt8500_get_mctrl
• function vt8500_set_mctrl
• function vt8500_break_ctl
• function vt8500_set_baud_rate
• function vt8500_startup
• function vt8500_shutdown
• function vt8500_set_termios
• function vt8500_release_port
• function vt8500_config_port
• function vt8500_verify_port
• function wait_for_xmitr
• function vt8500_console_putchar
• function vt8500_console_write
• function vt8500_console_setup
• function vt8500_get_poll_char
• function vt8500_put_poll_char
• function vt8500_serial_probe
• function vt8500_serial_init
• module init vt8500_serial_init

Annotated Snippet

device_initcall(vt8500_serial_init);

Annotation

• Immediate include surface: `linux/hrtimer.h`, `linux/delay.h`, `linux/io.h`, `linux/ioport.h`, `linux/irq.h`, `linux/init.h`, `linux/console.h`, `linux/platform_device.h`.
• Detected declarations: `struct vt8500_port`, `function vt8500_write`, `function vt8500_read`, `function vt8500_stop_tx`, `function vt8500_stop_rx`, `function vt8500_enable_ms`, `function handle_rx`, `function vt8500_tx_empty`, `function handle_tx`, `function vt8500_start_tx`.
• Atlas domain: Driver Families / drivers/tty.
• Implementation status: integration implementation candidate.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.