drivers/tty/serial/serial-tegra.c

File Facts

System

Linux kernel

Corpus path

drivers/tty/serial/serial-tegra.c

Extension

.c

Size

44894 bytes

Lines

1705

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/clk.h
• linux/debugfs.h
• linux/delay.h
• linux/dmaengine.h
• linux/dma-mapping.h
• linux/dmapool.h
• linux/err.h
• linux/io.h
• linux/irq.h
• linux/module.h
• linux/of.h
• linux/pagemap.h
• linux/platform_device.h
• linux/reset.h
• linux/serial.h
• linux/serial_8250.h
• linux/serial_core.h
• linux/serial_reg.h
• linux/slab.h
• linux/string.h
• linux/termios.h
• linux/tty.h
• linux/tty_flip.h

Detected Declarations

• struct tegra_uart_chip_data
• struct tegra_baud_tolerance
• struct tegra_uart_port
• function tegra_uart_read
• function tegra_uart_write
• function tegra_uart_get_mctrl
• function set_rts
• function set_dtr
• function set_loopbk
• function tegra_uart_set_mctrl
• function tegra_uart_break_ctl
• function tegra_uart_wait_cycle_time
• function tegra_uart_wait_sym_time
• function tegra_uart_wait_fifo_mode_enabled
• function tegra_uart_fifo_reset
• function tegra_get_tolerance_rate
• function tegra_check_rate_in_range
• function tegra_set_baudrate
• function tegra_uart_decode_rx_error
• function tegra_uart_request_port
• function tegra_uart_release_port
• function tegra_uart_start_pio_tx
• function tegra_uart_tx_dma_complete
• function tegra_uart_start_tx_dma
• function tegra_uart_start_next_tx
• function tegra_uart_start_tx
• function tegra_uart_tx_empty
• function tegra_uart_stop_tx
• function tegra_uart_handle_tx_pio
• function tegra_uart_handle_rx_pio
• function tegra_uart_copy_rx_to_tty
• function do_handle_rx_pio
• function tegra_uart_rx_buffer_push
• function tegra_uart_rx_dma_complete
• function tegra_uart_terminate_rx_dma
• function tegra_uart_handle_rx_dma
• function tegra_uart_start_rx_dma
• function tegra_uart_handle_modem_signal_change
• function tegra_uart_isr
• function tegra_uart_stop_rx
• function tegra_uart_hw_deinit
• function tegra_uart_hw_init
• function tegra_uart_dma_channel_free
• function tegra_uart_dma_channel_allocate
• function tegra_uart_startup
• function tegra_uart_flush_buffer
• function tegra_uart_shutdown
• function tegra_uart_enable_ms

Annotated Snippet

module_init(tegra_uart_init);
module_exit(tegra_uart_exit);

MODULE_ALIAS("platform:serial-tegra");
MODULE_DESCRIPTION("High speed UART driver for tegra chipset");
MODULE_AUTHOR("Laxman Dewangan <ldewangan@nvidia.com>");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/clk.h`, `linux/debugfs.h`, `linux/delay.h`, `linux/dmaengine.h`, `linux/dma-mapping.h`, `linux/dmapool.h`, `linux/err.h`, `linux/io.h`.
• Detected declarations: `struct tegra_uart_chip_data`, `struct tegra_baud_tolerance`, `struct tegra_uart_port`, `function tegra_uart_read`, `function tegra_uart_write`, `function tegra_uart_get_mctrl`, `function set_rts`, `function set_dtr`, `function set_loopbk`, `function tegra_uart_set_mctrl`.
• 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.