drivers/tty/serial/mcf.c

File Facts

System

Linux kernel

Corpus path

drivers/tty/serial/mcf.c

Extension

.c

Size

17931 bytes

Lines

663

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/kernel.h
• linux/init.h
• linux/interrupt.h
• linux/module.h
• linux/console.h
• linux/tty.h
• linux/tty_flip.h
• linux/serial.h
• linux/serial_core.h
• linux/io.h
• linux/uaccess.h
• linux/platform_device.h
• asm/coldfire.h
• asm/mcfsim.h
• asm/mcfuart.h
• asm/nettel.h

Detected Declarations

• struct mcf_uart
• function mcf_tx_empty
• function mcf_get_mctrl
• function mcf_set_mctrl
• function mcf_start_tx
• function mcf_stop_tx
• function mcf_stop_rx
• function mcf_break_ctl
• function mcf_startup
• function mcf_shutdown
• function mcf_set_termios
• function mcf_rx_chars
• function mcf_tx_chars
• function mcf_interrupt
• function mcf_config_port
• function mcf_request_port
• function mcf_release_port
• function mcf_config_rs485
• function mcf_console_putc
• function mcf_console_write
• function mcf_console_setup
• function mcf_console_init
• function mcf_probe
• function mcf_remove
• function mcf_init
• function mcf_exit
• module init mcf_init

Annotated Snippet

module_init(mcf_init);
module_exit(mcf_exit);

MODULE_AUTHOR("Greg Ungerer <gerg@uclinux.org>");
MODULE_DESCRIPTION("Freescale ColdFire UART driver");
MODULE_LICENSE("GPL");
MODULE_ALIAS("platform:mcfuart");

/****************************************************************************/

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/init.h`, `linux/interrupt.h`, `linux/module.h`, `linux/console.h`, `linux/tty.h`, `linux/tty_flip.h`, `linux/serial.h`.
• Detected declarations: `struct mcf_uart`, `function mcf_tx_empty`, `function mcf_get_mctrl`, `function mcf_set_mctrl`, `function mcf_start_tx`, `function mcf_stop_tx`, `function mcf_stop_rx`, `function mcf_break_ctl`, `function mcf_startup`, `function mcf_shutdown`.
• 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.