drivers/tty/serial/omap-serial.c

File Facts

System

Linux kernel

Corpus path

drivers/tty/serial/omap-serial.c

Extension

.c

Size

47849 bytes

Lines

1838

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/init.h
• linux/console.h
• linux/serial.h
• linux/serial_reg.h
• linux/delay.h
• linux/slab.h
• linux/tty.h
• linux/tty_flip.h
• linux/platform_device.h
• linux/io.h
• linux/clk.h
• linux/serial_core.h
• linux/irq.h
• linux/pm_runtime.h
• linux/pm_wakeirq.h
• linux/of.h
• linux/of_irq.h
• linux/gpio/consumer.h
• linux/platform_data/serial-omap.h

Detected Declarations

• struct uart_omap_dma
• struct uart_omap_port
• function serial_in
• function serial_out
• function serial_omap_clear_fifos
• function serial_omap_get_context_loss_count
• function serial_omap_enable_wakeup
• function calculate_baud_abs_diff
• function serial_omap_baud_is_mode16
• function serial_omap_get_divisor
• function serial_omap_enable_ms
• function serial_omap_stop_tx
• function serial_omap_stop_rx
• function serial_omap_put_char
• function transmit_chars
• function serial_omap_enable_ier_thri
• function serial_omap_start_tx
• function serial_omap_throttle
• function serial_omap_unthrottle
• function check_modem_status
• function serial_omap_rlsi
• function serial_omap_rdi
• function serial_omap_irq
• function serial_omap_tx_empty
• function serial_omap_get_mctrl
• function serial_omap_set_mctrl
• function serial_omap_break_ctl
• function serial_omap_startup
• function serial_omap_shutdown
• function serial_omap_uart_qos_work
• function serial_omap_set_termios
• function serial_omap_pm
• function serial_omap_release_port
• function serial_omap_request_port
• function serial_omap_config_port
• function serial_omap_verify_port
• function serial_omap_type
• function wait_for_xmitr
• function serial_omap_poll_put_char
• function serial_omap_poll_get_char
• function omap_serial_early_in
• function omap_serial_early_out
• function omap_serial_early_putc
• function early_omap_serial_write
• function early_omap_serial_setup
• function serial_omap_console_putchar
• function serial_omap_console_write
• function serial_omap_console_setup

Annotated Snippet

module_init(serial_omap_init);
module_exit(serial_omap_exit);

MODULE_DESCRIPTION("OMAP High Speed UART driver");
MODULE_LICENSE("GPL");
MODULE_AUTHOR("Texas Instruments Inc");

Annotation

• Immediate include surface: `linux/module.h`, `linux/init.h`, `linux/console.h`, `linux/serial.h`, `linux/serial_reg.h`, `linux/delay.h`, `linux/slab.h`, `linux/tty.h`.
• Detected declarations: `struct uart_omap_dma`, `struct uart_omap_port`, `function serial_in`, `function serial_out`, `function serial_omap_clear_fifos`, `function serial_omap_get_context_loss_count`, `function serial_omap_enable_wakeup`, `function calculate_baud_abs_diff`, `function serial_omap_baud_is_mode16`, `function serial_omap_get_divisor`.
• 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.