drivers/tty/serial/imx.c

File Facts

System

Linux kernel

Corpus path

drivers/tty/serial/imx.c

Extension

.c

Size

80119 bytes

Lines

2881

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/circ_buf.h
• linux/module.h
• linux/ioport.h
• linux/init.h
• linux/console.h
• linux/sysrq.h
• linux/platform_device.h
• linux/tty.h
• linux/tty_flip.h
• linux/serial_core.h
• linux/serial.h
• linux/clk.h
• linux/delay.h
• linux/ktime.h
• linux/pinctrl/consumer.h
• linux/rational.h
• linux/slab.h
• linux/of.h
• linux/io.h
• linux/iopoll.h
• linux/dma-mapping.h
• linux/irq.h
• linux/dma/imx-dma.h
• serial_mctrl_gpio.h

Detected Declarations

• struct imx_uart_data
• struct imx_port
• struct imx_port_ucrs
• enum imx_uart_type
• enum imx_tx_state
• function imx_uart_writel
• function imx_uart_readl
• function imx_uart_uts_reg
• function imx_uart_is_imx1
• function imx_uart_ucrs_save
• function imx_uart_ucrs_restore
• function imx_uart_rts_active
• function imx_uart_rts_inactive
• function start_hrtimer_ms
• function imx_uart_soft_reset
• function imx_uart_disable_loopback_rs485
• function imx_uart_start_rx
• function imx_uart_stop_tx
• function imx_uart_stop_rx_with_loopback_ctrl
• function imx_uart_stop_rx
• function imx_uart_enable_ms
• function imx_uart_transmit_buffer
• function imx_uart_dma_tx_callback
• function imx_uart_dma_tx
• function imx_uart_start_tx
• function imx_uart_stop_tx
• function __imx_uart_rtsint
• function imx_uart_rtsint
• function imx_uart_txint
• function flood
• function __imx_uart_rxint
• function imx_uart_rxint
• function imx_uart_get_hwmctrl
• function imx_uart_mctrl_check
• function imx_uart_int
• function imx_uart_tx_empty
• function imx_uart_get_mctrl
• function imx_uart_set_mctrl
• function imx_uart_break_ctl
• function imx_uart_timeout
• function interrupts
• function imx_uart_start_rx_dma
• function imx_uart_clear_rx_errors
• function imx_uart_setup_ufcr
• function imx_uart_dma_exit
• function imx_uart_dma_init
• function imx_uart_enable_dma
• function imx_uart_disable_dma

Annotated Snippet

module_init(imx_uart_init);
module_exit(imx_uart_exit);

MODULE_AUTHOR("Sascha Hauer");
MODULE_DESCRIPTION("IMX generic serial port driver");
MODULE_LICENSE("GPL");
MODULE_ALIAS("platform:imx-uart");

Annotation

• Immediate include surface: `linux/circ_buf.h`, `linux/module.h`, `linux/ioport.h`, `linux/init.h`, `linux/console.h`, `linux/sysrq.h`, `linux/platform_device.h`, `linux/tty.h`.
• Detected declarations: `struct imx_uart_data`, `struct imx_port`, `struct imx_port_ucrs`, `enum imx_uart_type`, `enum imx_tx_state`, `function imx_uart_writel`, `function imx_uart_readl`, `function imx_uart_uts_reg`, `function imx_uart_is_imx1`, `function imx_uart_ucrs_save`.
• 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.