drivers/tty/serial/men_z135_uart.c

File Facts

System

Linux kernel

Corpus path

drivers/tty/serial/men_z135_uart.c

Extension

.c

Size

21739 bytes

Lines

923

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/kernel.h
• linux/module.h
• linux/interrupt.h
• linux/serial_core.h
• linux/ioport.h
• linux/io.h
• linux/tty_flip.h
• linux/bitops.h
• linux/mcb.h

Detected Declarations

• struct men_z135_port
• function men_z135_reg_set
• function men_z135_reg_clr
• function men_z135_handle_modem_status
• function men_z135_handle_lsr
• function get_rx_fifo_content
• function men_z135_handle_rx
• function men_z135_handle_tx
• function men_z135_intr
• function men_z135_request_irq
• function men_z135_tx_empty
• function men_z135_set_mctrl
• function men_z135_get_mctrl
• function men_z135_stop_tx
• function men_z135_disable_ms
• function men_z135_start_tx
• function men_z135_stop_rx
• function men_z135_enable_ms
• function men_z135_startup
• function men_z135_shutdown
• function men_z135_set_termios
• function men_z135_release_port
• function men_z135_request_port
• function men_z135_config_port
• function men_z135_verify_port
• function men_z135_probe
• function men_z135_remove
• function men_z135_init
• function men_z135_exit
• module init men_z135_init

Annotated Snippet

module_init(men_z135_init);

/**
 * men_z135_exit() - Driver Exit Routine
 *
 * men_z135_exit is called just before the driver is removed from memory.
 */
static void __exit men_z135_exit(void)
{
	mcb_unregister_driver(&mcb_driver);
	uart_unregister_driver(&men_z135_driver);
}
module_exit(men_z135_exit);

MODULE_AUTHOR("Johannes Thumshirn <johannes.thumshirn@men.de>");
MODULE_LICENSE("GPL v2");
MODULE_DESCRIPTION("MEN 16z135 High Speed UART");
MODULE_IMPORT_NS("MCB");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/interrupt.h`, `linux/serial_core.h`, `linux/ioport.h`, `linux/io.h`, `linux/tty_flip.h`, `linux/bitops.h`.
• Detected declarations: `struct men_z135_port`, `function men_z135_reg_set`, `function men_z135_reg_clr`, `function men_z135_handle_modem_status`, `function men_z135_handle_lsr`, `function get_rx_fifo_content`, `function men_z135_handle_rx`, `function men_z135_handle_tx`, `function men_z135_intr`, `function men_z135_request_irq`.
• 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.