drivers/tty/serial/ar933x_uart.c

File Facts

System

Linux kernel

Corpus path

drivers/tty/serial/ar933x_uart.c

Extension

.c

Size

23131 bytes

Lines

941

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/module.h
• linux/ioport.h
• linux/init.h
• linux/console.h
• linux/sysrq.h
• linux/delay.h
• linux/gpio/consumer.h
• linux/platform_device.h
• linux/of.h
• linux/of_platform.h
• linux/tty.h
• linux/tty_flip.h
• linux/serial_core.h
• linux/serial.h
• linux/slab.h
• linux/io.h
• linux/irq.h
• linux/clk.h
• asm/div64.h
• asm/mach-ath79/ar933x_uart.h
• serial_mctrl_gpio.h

Detected Declarations

• struct ar933x_uart_port
• function ar933x_uart_read
• function ar933x_uart_write
• function ar933x_uart_rmw
• function ar933x_uart_rmw_set
• function ar933x_uart_rmw_clear
• function ar933x_uart_start_tx_interrupt
• function ar933x_uart_stop_tx_interrupt
• function ar933x_uart_start_rx_interrupt
• function ar933x_uart_stop_rx_interrupt
• function ar933x_uart_putc
• function ar933x_uart_tx_empty
• function ar933x_uart_get_mctrl
• function ar933x_uart_set_mctrl
• function ar933x_uart_start_tx
• function ar933x_uart_wait_tx_complete
• function ar933x_uart_rx_flush
• function ar933x_uart_stop_tx
• function ar933x_uart_stop_rx
• function ar933x_uart_break_ctl
• function ar933x_uart_get_baud
• function ar933x_uart_get_scale_step
• function ar933x_uart_set_termios
• function ar933x_uart_rx_chars
• function ar933x_uart_tx_chars
• function ar933x_uart_interrupt
• function ar933x_uart_startup
• function ar933x_uart_shutdown
• function ar933x_uart_release_port
• function ar933x_uart_config_port
• function ar933x_uart_verify_port
• function ar933x_poll_get_char
• function ar933x_poll_put_char
• function ar933x_config_rs485
• function ar933x_uart_wait_xmitr
• function ar933x_uart_console_putchar
• function ar933x_uart_console_write
• function ar933x_uart_console_setup
• function ar933x_uart_probe
• function ar933x_uart_remove
• function ar933x_uart_init
• function ar933x_uart_exit
• module init ar933x_uart_init

Annotated Snippet

module_init(ar933x_uart_init);
module_exit(ar933x_uart_exit);

MODULE_DESCRIPTION("Atheros AR933X UART driver");
MODULE_AUTHOR("Gabor Juhos <juhosg@openwrt.org>");
MODULE_LICENSE("GPL v2");
MODULE_ALIAS("platform:" DRIVER_NAME);

Annotation

• Immediate include surface: `linux/module.h`, `linux/ioport.h`, `linux/init.h`, `linux/console.h`, `linux/sysrq.h`, `linux/delay.h`, `linux/gpio/consumer.h`, `linux/platform_device.h`.
• Detected declarations: `struct ar933x_uart_port`, `function ar933x_uart_read`, `function ar933x_uart_write`, `function ar933x_uart_rmw`, `function ar933x_uart_rmw_set`, `function ar933x_uart_rmw_clear`, `function ar933x_uart_start_tx_interrupt`, `function ar933x_uart_stop_tx_interrupt`, `function ar933x_uart_start_rx_interrupt`, `function ar933x_uart_stop_rx_interrupt`.
• 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.