drivers/tty/serial/tegra-utc.c

File Facts

System

Linux kernel

Corpus path

drivers/tty/serial/tegra-utc.c

Extension

.c

Size

16848 bytes

Lines

626

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/bits.h
• linux/console.h
• linux/container_of.h
• linux/device.h
• linux/err.h
• linux/iopoll.h
• linux/kfifo.h
• linux/module.h
• linux/mod_devicetable.h
• linux/property.h
• linux/platform_device.h
• linux/serial.h
• linux/serial_core.h
• linux/slab.h
• linux/tty.h
• linux/tty_flip.h
• linux/types.h

Detected Declarations

• struct tegra_utc_port
• function tegra_utc_rx_readl
• function tegra_utc_rx_writel
• function tegra_utc_tx_readl
• function tegra_utc_tx_writel
• function tegra_utc_enable_tx_irq
• function tegra_utc_disable_tx_irq
• function tegra_utc_stop_tx
• function tegra_utc_init_tx
• function tegra_utc_init_rx
• function tegra_utc_tx_chars
• function tegra_utc_rx_chars
• function tegra_utc_isr
• function tegra_utc_tx_empty
• function tegra_utc_set_mctrl
• function tegra_utc_start_tx
• function tegra_utc_stop_rx
• function tegra_utc_hw_init
• function tegra_utc_startup
• function tegra_utc_shutdown
• function tegra_utc_set_termios
• function tegra_utc_poll_init
• function tegra_utc_get_poll_char
• function tegra_utc_put_poll_char
• function tegra_utc_putc
• function tegra_utc_early_write
• function tegra_utc_early_console_setup
• function tegra_utc_console_putchar
• function tegra_utc_console_write_atomic
• function tegra_utc_console_write_thread
• function tegra_utc_console_device_lock
• function tegra_utc_console_device_unlock
• function tegra_utc_console_setup
• function tegra_utc_setup_port
• function tegra_utc_register_port
• function tegra_utc_probe
• function tegra_utc_remove
• function tegra_utc_init
• function tegra_utc_exit
• module init tegra_utc_init

Annotated Snippet

module_init(tegra_utc_init);

static void __exit tegra_utc_exit(void)
{
	platform_driver_unregister(&tegra_utc_platform_driver);
	uart_unregister_driver(&tegra_utc_driver);
}
module_exit(tegra_utc_exit);

MODULE_AUTHOR("Kartik Rajput <kkartik@nvidia.com>");
MODULE_DESCRIPTION("Tegra UART Trace Controller");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/bits.h`, `linux/console.h`, `linux/container_of.h`, `linux/device.h`, `linux/err.h`, `linux/iopoll.h`, `linux/kfifo.h`, `linux/module.h`.
• Detected declarations: `struct tegra_utc_port`, `function tegra_utc_rx_readl`, `function tegra_utc_rx_writel`, `function tegra_utc_tx_readl`, `function tegra_utc_tx_writel`, `function tegra_utc_enable_tx_irq`, `function tegra_utc_disable_tx_irq`, `function tegra_utc_stop_tx`, `function tegra_utc_init_tx`, `function tegra_utc_init_rx`.
• 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.