drivers/tty/serial/atmel_serial.c
Source file repositories/reference/linux-study-clean/drivers/tty/serial/atmel_serial.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/tty/serial/atmel_serial.c- Extension
.c- Size
- 82083 bytes
- Lines
- 3027
- 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/circ_buf.hlinux/tty.hlinux/ioport.hlinux/slab.hlinux/init.hlinux/serial.hlinux/clk.hlinux/clk-provider.hlinux/console.hlinux/sysrq.hlinux/tty_flip.hlinux/platform_device.hlinux/of.hlinux/dma-mapping.hlinux/dmaengine.hlinux/atmel_pdc.hlinux/uaccess.hlinux/platform_data/atmel.hlinux/timer.hlinux/err.hlinux/irq.hlinux/suspend.hlinux/mm.hlinux/io.hasm/div64.hasm/ioctls.hlinux/serial_core.hserial_mctrl_gpio.hatmel_serial.h
Detected Declarations
struct atmel_dma_bufferstruct atmel_uart_charstruct atmel_uart_portfunction to_atmel_uart_portfunction atmel_uart_readlfunction atmel_uart_writelfunction atmel_uart_read_charfunction atmel_uart_write_charfunction atmel_uart_is_half_duplexfunction atmel_error_ratefunction atmel_use_pdc_rxfunction atmel_use_pdc_txfunction atmel_use_pdc_rxfunction atmel_use_pdc_txfunction atmel_use_dma_txfunction atmel_use_dma_rxfunction atmel_use_fifofunction atmel_tasklet_schedulefunction atmel_config_rs485function atmel_calc_cdfunction atmel_calc_fidifunction atmel_config_iso7816function atmel_tx_emptyfunction atmel_set_mctrlfunction atmel_get_mctrlfunction atmel_stop_txfunction atmel_start_txfunction atmel_start_rxfunction atmel_stop_rxfunction atmel_enable_msfunction atmel_disable_msfunction atmel_break_ctlfunction atmel_buffer_rx_charfunction atmel_pdc_rxerrfunction receivedfunction charactersfunction atmel_complete_tx_dmafunction atmel_release_tx_dmafunction atmel_tx_dmafunction atmel_prepare_tx_dmafunction atmel_complete_rx_dmafunction atmel_release_rx_dmafunction atmel_rx_from_dmafunction atmel_prepare_rx_dmafunction atmel_uart_timer_callbackfunction atmel_handle_receivefunction atmel_handle_transmitfunction atmel_handle_status
Annotated Snippet
device_initcall(atmel_serial_init);
Annotation
- Immediate include surface: `linux/circ_buf.h`, `linux/tty.h`, `linux/ioport.h`, `linux/slab.h`, `linux/init.h`, `linux/serial.h`, `linux/clk.h`, `linux/clk-provider.h`.
- Detected declarations: `struct atmel_dma_buffer`, `struct atmel_uart_char`, `struct atmel_uart_port`, `function to_atmel_uart_port`, `function atmel_uart_readl`, `function atmel_uart_writel`, `function atmel_uart_read_char`, `function atmel_uart_write_char`, `function atmel_uart_is_half_duplex`, `function atmel_error_rate`.
- 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.