drivers/mmc/core/sdio_uart.c

File Facts

System

Linux kernel

Corpus path

drivers/mmc/core/sdio_uart.c

Extension

.c

Size

28805 bytes

Lines

1167

Domain

Driver Families

Bucket

drivers/mmc

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/init.h
• linux/kernel.h
• linux/sched.h
• linux/mutex.h
• linux/seq_file.h
• linux/serial.h
• linux/serial_reg.h
• linux/circ_buf.h
• linux/tty.h
• linux/tty_flip.h
• linux/kfifo.h
• linux/slab.h
• linux/mmc/core.h
• linux/mmc/card.h
• linux/mmc/sdio_func.h
• linux/mmc/sdio_ids.h

Detected Declarations

• struct uart_icount
• struct sdio_uart_port
• function sdio_uart_add_port
• function sdio_uart_port_put
• function sdio_uart_port_remove
• function sdio_uart_claim_func
• function sdio_uart_release_func
• function sdio_in
• function sdio_out
• function sdio_uart_get_mctrl
• function sdio_uart_write_mctrl
• function sdio_uart_update_mctrl
• function sdio_uart_change_speed
• function sdio_uart_start_tx
• function sdio_uart_stop_tx
• function sdio_uart_stop_rx
• function sdio_uart_receive_chars
• function sdio_uart_transmit_chars
• function sdio_uart_check_modem_status
• function sdio_uart_irq
• function uart_carrier_raised
• function uart_dtr_rts
• function sdio_uart_activate
• function sdio_uart_shutdown
• function sdio_uart_port_destroy
• function data
• function sdio_uart_cleanup
• function sdio_uart_open
• function sdio_uart_close
• function sdio_uart_hangup
• function sdio_uart_write
• function sdio_uart_write_room
• function sdio_uart_chars_in_buffer
• function sdio_uart_send_xchar
• function sdio_uart_throttle
• function sdio_uart_unthrottle
• function sdio_uart_set_termios
• function sdio_uart_break_ctl
• function sdio_uart_tiocmget
• function sdio_uart_tiocmset
• function sdio_uart_proc_show
• function sdio_uart_probe
• function sdio_uart_remove
• function sdio_uart_init
• function sdio_uart_exit
• module init sdio_uart_init

Annotated Snippet

module_init(sdio_uart_init);
module_exit(sdio_uart_exit);

MODULE_AUTHOR("Nicolas Pitre");
MODULE_DESCRIPTION("SDIO UART/GPS driver");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/module.h`, `linux/init.h`, `linux/kernel.h`, `linux/sched.h`, `linux/mutex.h`, `linux/seq_file.h`, `linux/serial.h`, `linux/serial_reg.h`.
• Detected declarations: `struct uart_icount`, `struct sdio_uart_port`, `function sdio_uart_add_port`, `function sdio_uart_port_put`, `function sdio_uart_port_remove`, `function sdio_uart_claim_func`, `function sdio_uart_release_func`, `function sdio_in`, `function sdio_out`, `function sdio_uart_get_mctrl`.
• Atlas domain: Driver Families / drivers/mmc.
• 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.