drivers/tty/serial/zs.c

File Facts

System

Linux kernel

Corpus path

drivers/tty/serial/zs.c

Extension

.c

Size

30517 bytes

Lines

1249

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/bug.h
• linux/console.h
• linux/delay.h
• linux/errno.h
• linux/init.h
• linux/interrupt.h
• linux/io.h
• linux/ioport.h
• linux/irqflags.h
• linux/kernel.h
• linux/module.h
• linux/major.h
• linux/platform_device.h
• linux/serial.h
• linux/serial_core.h
• linux/spinlock.h
• linux/sysrq.h
• linux/tty.h
• linux/tty_flip.h
• linux/types.h
• linux/atomic.h
• zs.h

Detected Declarations

• function recovery_delay
• function read_zsreg
• function write_zsreg
• function read_zsdata
• function write_zsdata
• function zs_dump
• function zs_spin_lock_cond_irq
• function zs_spin_unlock_cond_irq
• function zs_receive_drain
• function zs_transmit_drain
• function zs_line_drain
• function load_zsregs
• function zs_tx_empty
• function zs_raw_get_ab_mctrl
• function zs_raw_get_mctrl
• function zs_raw_xor_mctrl
• function zs_get_mctrl
• function zs_set_mctrl
• function zs_raw_stop_tx
• function zs_stop_tx
• function zs_start_tx
• function zs_stop_rx
• function zs_enable_ms
• function zs_break_ctl
• function zs_receive_chars
• function zs_raw_transmit_chars
• function zs_transmit_chars
• function zs_status_handle
• function zs_interrupt
• function zs_startup
• function zs_shutdown
• function zs_reset
• function zs_set_termios
• function zs_release_port
• function zs_map_port
• function zs_request_port
• function zs_config_port
• function zs_verify_port
• function zs_probe
• function zs_remove
• function zs_console_putchar
• function zs_console_write
• function zs_console_setup
• function zs_init
• function zs_exit
• module init zs_init

Annotated Snippet

module_init(zs_init);
module_exit(zs_exit);

Annotation

• Immediate include surface: `linux/bug.h`, `linux/console.h`, `linux/delay.h`, `linux/errno.h`, `linux/init.h`, `linux/interrupt.h`, `linux/io.h`, `linux/ioport.h`.
• Detected declarations: `function recovery_delay`, `function read_zsreg`, `function write_zsreg`, `function read_zsdata`, `function write_zsdata`, `function zs_dump`, `function zs_spin_lock_cond_irq`, `function zs_spin_unlock_cond_irq`, `function zs_receive_drain`, `function zs_transmit_drain`.
• Atlas domain: Driver Families / drivers/tty.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• 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.