drivers/tty/serial/ip22zilog.c

File Facts

System

Linux kernel

Corpus path

drivers/tty/serial/ip22zilog.c

Extension

.c

Size

29460 bytes

Lines

1154

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/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/init.h
• linux/platform_device.h
• linux/io.h
• asm/irq.h
• asm/sgialib.h
• asm/sgi/ioc.h
• asm/sgi/hpc3.h
• asm/sgi/ip22.h
• linux/serial_core.h
• ip22zilog.h

Detected Declarations

• struct uart_ip22zilog_port
• function read_zsreg
• function write_zsreg
• function ip22zilog_clear_fifo
• function __load_zsregs
• function ip22zilog_maybe_update_regs
• function ip22zilog_receive_chars
• function ip22zilog_status_handle
• function ip22zilog_transmit_chars
• function ip22zilog_interrupt
• function ip22zilog_read_channel_status
• function ip22zilog_tx_empty
• function ip22zilog_get_mctrl
• function ip22zilog_set_mctrl
• function ip22zilog_stop_tx
• function ip22zilog_start_tx
• function ip22zilog_stop_rx
• function ip22zilog_enable_ms
• function ip22zilog_break_ctl
• function __ip22zilog_reset
• function __ip22zilog_startup
• function ip22zilog_startup
• function memory
• function ip22zilog_convert_to_zs
• function ip22zilog_set_termios
• function ip22zilog_release_port
• function ip22zilog_config_port
• function ip22zilog_put_char
• function ip22zilog_console_write
• function ip22zilog_console_setup
• function ip22zilog_prepare
• function ip22zilog_probe
• function ip22zilog_remove
• function ip22zilog_init
• function ip22zilog_exit
• module init ip22zilog_init

Annotated Snippet

module_init(ip22zilog_init);
module_exit(ip22zilog_exit);

/* David wrote it but I'm to blame for the bugs ...  */
MODULE_AUTHOR("Ralf Baechle <ralf@linux-mips.org>");
MODULE_DESCRIPTION("SGI Zilog serial port driver");
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_ip22zilog_port`, `function read_zsreg`, `function write_zsreg`, `function ip22zilog_clear_fifo`, `function __load_zsregs`, `function ip22zilog_maybe_update_regs`, `function ip22zilog_receive_chars`, `function ip22zilog_status_handle`, `function ip22zilog_transmit_chars`, `function ip22zilog_interrupt`.
• 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.