drivers/tty/serial/digicolor-usart.c

File Facts

System

Linux kernel

Corpus path

drivers/tty/serial/digicolor-usart.c

Extension

.c

Size

14175 bytes

Lines

559

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/module.h
• linux/console.h
• linux/serial_core.h
• linux/serial.h
• linux/clk.h
• linux/io.h
• linux/tty.h
• linux/tty_flip.h
• linux/of.h
• linux/platform_device.h
• linux/workqueue.h

Detected Declarations

• struct digicolor_port
• function digicolor_uart_tx_full
• function digicolor_uart_rx_empty
• function digicolor_uart_stop_tx
• function digicolor_uart_start_tx
• function digicolor_uart_stop_rx
• function digicolor_rx_poll
• function digicolor_uart_rx
• function digicolor_uart_tx
• function digicolor_uart_int
• function digicolor_uart_tx_empty
• function digicolor_uart_get_mctrl
• function digicolor_uart_set_mctrl
• function digicolor_uart_shutdown
• function digicolor_uart_set_termios
• function digicolor_uart_config_port
• function digicolor_uart_release_port
• function digicolor_uart_console_putchar
• function digicolor_uart_console_write
• function digicolor_uart_console_setup
• function digicolor_uart_probe
• function digicolor_uart_remove
• function digicolor_uart_init
• function digicolor_uart_exit
• module init digicolor_uart_init

Annotated Snippet

module_init(digicolor_uart_init);

static void __exit digicolor_uart_exit(void)
{
	platform_driver_unregister(&digicolor_uart_platform);
	uart_unregister_driver(&digicolor_uart);
}
module_exit(digicolor_uart_exit);

MODULE_AUTHOR("Baruch Siach <baruch@tkos.co.il>");
MODULE_DESCRIPTION("Conexant Digicolor USART serial driver");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/module.h`, `linux/console.h`, `linux/serial_core.h`, `linux/serial.h`, `linux/clk.h`, `linux/io.h`, `linux/tty.h`, `linux/tty_flip.h`.
• Detected declarations: `struct digicolor_port`, `function digicolor_uart_tx_full`, `function digicolor_uart_rx_empty`, `function digicolor_uart_stop_tx`, `function digicolor_uart_start_tx`, `function digicolor_uart_stop_rx`, `function digicolor_rx_poll`, `function digicolor_uart_rx`, `function digicolor_uart_tx`, `function digicolor_uart_int`.
• 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.