drivers/tty/serial/sunzilog.c

File Facts

System

Linux kernel

Corpus path

drivers/tty/serial/sunzilog.c

Extension

.c

Size

41512 bytes

Lines

1647

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.
• 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/module.h
• linux/kernel.h
• linux/errno.h
• linux/delay.h
• linux/tty.h
• linux/tty_flip.h
• linux/major.h
• linux/string.h
• linux/ptrace.h
• linux/ioport.h
• linux/slab.h
• linux/circ_buf.h
• linux/serial.h
• linux/sysrq.h
• linux/console.h
• linux/spinlock.h
• linux/serio.h
• linux/init.h
• linux/of.h
• linux/platform_device.h
• linux/io.h
• asm/irq.h
• asm/setup.h
• linux/serial_core.h
• linux/sunserialcore.h
• sunzilog.h

Detected Declarations

• struct uart_sunzilog_port
• function read_zsreg
• function write_zsreg
• function sunzilog_clear_fifo
• function __load_zsregs
• function sunzilog_maybe_update_regs
• function sunzilog_change_mouse_baud
• function sunzilog_kbdms_receive_chars
• function sunzilog_receive_chars
• function sunzilog_status_handle
• function sunzilog_transmit_chars
• function sunzilog_interrupt
• function sunzilog_read_channel_status
• function sunzilog_tx_empty
• function sunzilog_get_mctrl
• function sunzilog_set_mctrl
• function sunzilog_stop_tx
• function sunzilog_start_tx
• function sunzilog_stop_rx
• function sunzilog_enable_ms
• function sunzilog_break_ctl
• function __sunzilog_startup
• function sunzilog_startup
• function memory
• function sunzilog_convert_to_zs
• function sunzilog_set_termios
• function sunzilog_release_port
• function sunzilog_config_port
• function sunzilog_get_poll_char
• function sunzilog_put_poll_char
• function sunzilog_alloc_tables
• function sunzilog_free_tables
• function sunzilog_putchar
• function sunzilog_serio_write
• function sunzilog_serio_open
• function sunzilog_serio_close
• function sunzilog_console_write
• function sunzilog_console_setup
• function sunzilog_init_kbdms
• function sunzilog_register_serio
• function sunzilog_init_hw
• function zs_probe
• function zs_remove_one
• function zs_remove
• function sunzilog_init
• function for_each_node_by_name
• function sunzilog_exit
• module init sunzilog_init

Annotated Snippet

module_init(sunzilog_init);
module_exit(sunzilog_exit);

MODULE_AUTHOR("David S. Miller");
MODULE_DESCRIPTION("Sun Zilog serial port driver");
MODULE_VERSION("2.0");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/module.h`, `linux/kernel.h`, `linux/errno.h`, `linux/delay.h`, `linux/tty.h`, `linux/tty_flip.h`, `linux/major.h`, `linux/string.h`.
• Detected declarations: `struct uart_sunzilog_port`, `function read_zsreg`, `function write_zsreg`, `function sunzilog_clear_fifo`, `function __load_zsregs`, `function sunzilog_maybe_update_regs`, `function sunzilog_change_mouse_baud`, `function sunzilog_kbdms_receive_chars`, `function sunzilog_receive_chars`, `function sunzilog_status_handle`.
• 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.