drivers/tty/serial/ma35d1_serial.c

File Facts

System

Linux kernel

Corpus path

drivers/tty/serial/ma35d1_serial.c

Extension

.c

Size

23477 bytes

Lines

832

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

Dependency Surface

• linux/bitfield.h
• linux/clk.h
• linux/delay.h
• linux/of.h
• linux/platform_device.h
• linux/iopoll.h
• linux/serial_core.h
• linux/slab.h
• linux/tty_flip.h
• linux/units.h

Detected Declarations

• struct uart_ma35d1_port
• function serial_in
• function serial_out
• function __stop_tx
• function ma35d1serial_stop_tx
• function transmit_chars
• function ma35d1serial_start_tx
• function ma35d1serial_stop_rx
• function receive_chars
• function ma35d1serial_interrupt
• function ma35d1serial_tx_empty
• function ma35d1serial_get_mctrl
• function ma35d1serial_set_mctrl
• function ma35d1serial_break_ctl
• function ma35d1serial_startup
• function ma35d1serial_shutdown
• function ma35d1serial_set_termios
• function ma35d1serial_config_port
• function ma35d1serial_verify_port
• function wait_for_xmitr
• function ma35d1serial_console_putchar
• function ma35d1serial_console_write
• function ma35d1serial_console_setup
• function ma35d1serial_console_init_port
• function for_each_matching_node
• function ma35d1serial_console_init
• function ma35d1serial_probe
• function ma35d1serial_remove
• function ma35d1serial_suspend
• function ma35d1serial_resume
• function ma35d1serial_init
• function ma35d1serial_exit
• module init ma35d1serial_init

Annotated Snippet

module_init(ma35d1serial_init);
module_exit(ma35d1serial_exit);

MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("MA35D1 serial driver");

Annotation

• Immediate include surface: `linux/bitfield.h`, `linux/clk.h`, `linux/delay.h`, `linux/of.h`, `linux/platform_device.h`, `linux/iopoll.h`, `linux/serial_core.h`, `linux/slab.h`.
• Detected declarations: `struct uart_ma35d1_port`, `function serial_in`, `function serial_out`, `function __stop_tx`, `function ma35d1serial_stop_tx`, `function transmit_chars`, `function ma35d1serial_start_tx`, `function ma35d1serial_stop_rx`, `function receive_chars`, `function ma35d1serial_interrupt`.
• 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.