drivers/tty/serial/msm_serial.c

File Facts

System

Linux kernel

Corpus path

drivers/tty/serial/msm_serial.c

Extension

.c

Size

47995 bytes

Lines

1941

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/kernel.h
• linux/atomic.h
• linux/dma/qcom_adm.h
• linux/dma-mapping.h
• linux/dmaengine.h
• linux/module.h
• linux/io.h
• linux/ioport.h
• linux/interrupt.h
• linux/init.h
• linux/console.h
• linux/tty.h
• linux/tty_flip.h
• linux/serial_core.h
• linux/slab.h
• linux/clk.h
• linux/platform_device.h
• linux/pm_opp.h
• linux/delay.h
• linux/of.h
• linux/of_device.h
• linux/wait.h

Detected Declarations

• struct msm_dma
• struct msm_port
• struct msm_baud_map
• function msm_write
• function msm_read
• function msm_serial_set_mnd_regs_tcxo
• function msm_serial_set_mnd_regs_tcxoby4
• function msm_serial_set_mnd_regs
• function msm_stop_dma
• function msm_release_dma
• function msm_request_tx_dma
• function msm_request_rx_dma
• function msm_wait_for_xmitr
• function msm_stop_tx
• function msm_start_tx
• function msm_reset_dm_count
• function msm_complete_tx_dma
• function msm_handle_tx_dma
• function msm_complete_rx_dma
• function msm_start_rx_dma
• function msm_stop_rx
• function msm_enable_ms
• function msm_handle_rx_dm
• function msm_handle_rx
• function msm_handle_tx_pio
• function msm_handle_tx
• function msm_handle_delta_cts
• function msm_uart_irq
• function msm_tx_empty
• function msm_get_mctrl
• function msm_reset
• function msm_set_mctrl
• function msm_break_ctl
• function msm_find_best_baud
• function msm_set_baud_rate
• function msm_init_clock
• function msm_startup
• function msm_shutdown
• function msm_set_termios
• function msm_release_port
• function msm_request_port
• function msm_config_port
• function msm_verify_port
• function msm_power
• function msm_poll_get_char_single
• function msm_poll_get_char_dm
• function msm_poll_get_char
• function msm_poll_put_char

Annotated Snippet

module_init(msm_serial_init);
module_exit(msm_serial_exit);

MODULE_AUTHOR("Robert Love <rlove@google.com>");
MODULE_DESCRIPTION("Driver for msm7x serial device");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/atomic.h`, `linux/dma/qcom_adm.h`, `linux/dma-mapping.h`, `linux/dmaengine.h`, `linux/module.h`, `linux/io.h`, `linux/ioport.h`.
• Detected declarations: `struct msm_dma`, `struct msm_port`, `struct msm_baud_map`, `function msm_write`, `function msm_read`, `function msm_serial_set_mnd_regs_tcxo`, `function msm_serial_set_mnd_regs_tcxoby4`, `function msm_serial_set_mnd_regs`, `function msm_stop_dma`, `function msm_release_dma`.
• 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.