drivers/tty/serial/apbuart.c

File Facts

System

Linux kernel

Corpus path

drivers/tty/serial/apbuart.c

Extension

.c

Size

15664 bytes

Lines

663

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/tty.h
• linux/tty_flip.h
• linux/ioport.h
• linux/init.h
• linux/serial.h
• linux/console.h
• linux/sysrq.h
• linux/kthread.h
• linux/device.h
• linux/of.h
• linux/platform_device.h
• linux/io.h
• linux/serial_core.h
• asm/irq.h
• apbuart.h

Detected Declarations

• function apbuart_stop_tx
• function apbuart_start_tx
• function apbuart_stop_rx
• function apbuart_rx_chars
• function apbuart_tx_chars
• function apbuart_int
• function apbuart_tx_empty
• function apbuart_get_mctrl
• function apbuart_set_mctrl
• function apbuart_shutdown
• function apbuart_set_termios
• function apbuart_release_port
• function apbuart_request_port
• function apbuart_config_port
• function apbuart_verify_port
• function apbuart_scan_fifo_size
• function apbuart_flush_fifo
• function apbuart_console_putchar
• function apbuart_console_write
• function apbuart_console_get_options
• function apbuart_console_setup
• function apbuart_console_init
• function apbuart_probe
• function grlib_apbuart_configure
• function for_each_matching_node
• function grlib_apbuart_init
• function grlib_apbuart_exit
• module init grlib_apbuart_init

Annotated Snippet

module_init(grlib_apbuart_init);
module_exit(grlib_apbuart_exit);

MODULE_AUTHOR("Aeroflex Gaisler AB");
MODULE_DESCRIPTION("GRLIB APBUART serial driver");
MODULE_VERSION("2.1");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/module.h`, `linux/tty.h`, `linux/tty_flip.h`, `linux/ioport.h`, `linux/init.h`, `linux/serial.h`, `linux/console.h`, `linux/sysrq.h`.
• Detected declarations: `function apbuart_stop_tx`, `function apbuart_start_tx`, `function apbuart_stop_rx`, `function apbuart_rx_chars`, `function apbuart_tx_chars`, `function apbuart_int`, `function apbuart_tx_empty`, `function apbuart_get_mctrl`, `function apbuart_set_mctrl`, `function apbuart_shutdown`.
• 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.