drivers/tty/serial/mxs-auart.c

File Facts

System

Linux kernel

Corpus path

drivers/tty/serial/mxs-auart.c

Extension

.c

Size

44914 bytes

Lines

1745

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/kernel.h
• linux/errno.h
• linux/init.h
• linux/console.h
• linux/interrupt.h
• linux/module.h
• linux/slab.h
• linux/wait.h
• linux/tty.h
• linux/tty_driver.h
• linux/tty_flip.h
• linux/serial.h
• linux/serial_core.h
• linux/platform_device.h
• linux/device.h
• linux/clk.h
• linux/delay.h
• linux/io.h
• linux/of.h
• linux/dma-mapping.h
• linux/dmaengine.h
• linux/gpio/consumer.h
• linux/err.h
• linux/irq.h
• serial_mctrl_gpio.h

Detected Declarations

• struct vendor_data
• struct mxs_auart_port
• enum mxs_auart_type
• function is_imx28_auart
• function is_asm9260_auart
• function auart_dma_enabled
• function mxs_reg_to_offset
• function mxs_read
• function mxs_write
• function mxs_set
• function mxs_clr
• function dma_tx_callback
• function mxs_auart_dma_tx
• function mxs_auart_tx_chars
• function mxs_auart_rx_char
• function mxs_auart_rx_chars
• function mxs_auart_request_port
• function mxs_auart_verify_port
• function mxs_auart_config_port
• function mxs_auart_release_port
• function mxs_auart_modem_status
• function mxs_auart_get_mctrl
• function mxs_auart_enable_ms
• function mxs_auart_disable_ms
• function dma_rx_callback
• function mxs_auart_dma_prep_rx
• function mxs_auart_dma_exit_channel
• function mxs_auart_dma_exit
• function mxs_auart_dma_init
• function mxs_auart_settermios
• function bug
• function mxs_auart_set_ldisc
• function mxs_auart_irq_handle
• function mxs_auart_reset_deassert
• function mxs_auart_reset_assert
• function mxs_auart_startup
• function mxs_auart_shutdown
• function mxs_auart_tx_empty
• function mxs_auart_start_tx
• function mxs_auart_stop_tx
• function mxs_auart_stop_rx
• function mxs_auart_break_ctl
• function mxs_auart_console_putchar
• function auart_console_write
• function auart_console_get_options
• function auart_console_setup
• function mxs_init_regs
• function mxs_get_clks

Annotated Snippet

module_init(mxs_auart_init);
module_exit(mxs_auart_exit);
MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("Freescale MXS application uart driver");
MODULE_ALIAS("platform:mxs-auart");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/errno.h`, `linux/init.h`, `linux/console.h`, `linux/interrupt.h`, `linux/module.h`, `linux/slab.h`, `linux/wait.h`.
• Detected declarations: `struct vendor_data`, `struct mxs_auart_port`, `enum mxs_auart_type`, `function is_imx28_auart`, `function is_asm9260_auart`, `function auart_dma_enabled`, `function mxs_reg_to_offset`, `function mxs_read`, `function mxs_write`, `function mxs_set`.
• 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.