drivers/tty/serial/uartlite.c

File Facts

System

Linux kernel

Corpus path

drivers/tty/serial/uartlite.c

Extension

.c

Size

22728 bytes

Lines

950

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.
• 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/platform_device.h
• linux/module.h
• linux/bitfield.h
• linux/console.h
• linux/serial.h
• linux/serial_core.h
• linux/tty.h
• linux/tty_flip.h
• linux/delay.h
• linux/interrupt.h
• linux/init.h
• linux/io.h
• linux/iopoll.h
• linux/of.h
• linux/clk.h
• linux/pm_runtime.h

Detected Declarations

• struct uartlite_data
• struct uartlite_reg_ops
• function uartlite_inbe32
• function uartlite_outbe32
• function uartlite_inle32
• function uartlite_outle32
• function uart_in32
• function uart_out32
• function ulite_receive
• function ulite_transmit
• function ulite_isr
• function ulite_tx_empty
• function ulite_get_mctrl
• function ulite_set_mctrl
• function ulite_stop_rx
• function ulite_break_ctl
• function ulite_shutdown
• function ulite_set_termios
• function ulite_release_port
• function ulite_request_port
• function ulite_config_port
• function ulite_verify_port
• function ulite_pm
• function ulite_get_poll_char
• function ulite_put_poll_char
• function ulite_console_wait_tx
• function ulite_console_putchar
• function ulite_console_write
• function ulite_console_setup
• function early_uartlite_putc
• function early_uartlite_write
• function early_uartlite_setup
• function functions
• function ulite_release
• function ulite_suspend
• function ulite_resume
• function ulite_runtime_suspend
• function ulite_runtime_resume
• function ulite_probe
• function ulite_remove
• function ulite_init
• function ulite_exit
• module init ulite_init

Annotated Snippet

module_init(ulite_init);
module_exit(ulite_exit);

MODULE_AUTHOR("Peter Korsgaard <jacmet@sunsite.dk>");
MODULE_DESCRIPTION("Xilinx uartlite serial driver");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/platform_device.h`, `linux/module.h`, `linux/bitfield.h`, `linux/console.h`, `linux/serial.h`, `linux/serial_core.h`, `linux/tty.h`, `linux/tty_flip.h`.
• Detected declarations: `struct uartlite_data`, `struct uartlite_reg_ops`, `function uartlite_inbe32`, `function uartlite_outbe32`, `function uartlite_inle32`, `function uartlite_outle32`, `function uart_in32`, `function uart_out32`, `function ulite_receive`, `function ulite_transmit`.
• 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.