drivers/mmc/host/au1xmmc.c

File Facts

System

Linux kernel

Corpus path

drivers/mmc/host/au1xmmc.c

Extension

.c

Size

29392 bytes

Lines

1216

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.
• 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/clk.h
• linux/module.h
• linux/init.h
• linux/platform_device.h
• linux/mm.h
• linux/interrupt.h
• linux/dma-mapping.h
• linux/scatterlist.h
• linux/highmem.h
• linux/leds.h
• linux/mmc/host.h
• linux/slab.h
• linux/workqueue.h
• asm/io.h
• asm/mach-au1x00/au1000.h
• asm/mach-au1x00/au1xxx_dbdma.h
• asm/mach-au1x00/au1100_mmc.h

Detected Declarations

• struct au1xmmc_host
• function has_dbdma
• function IRQ_ON
• function FLUSH_FIFO
• function IRQ_OFF
• function SEND_STOP
• function au1xmmc_set_power
• function au1xmmc_card_inserted
• function au1xmmc_card_readonly
• function au1xmmc_finish_request
• function au1xmmc_finish_bh_work
• function au1xmmc_send_command
• function au1xmmc_data_complete
• function au1xmmc_data_bh_work
• function au1xmmc_send_pio
• function au1xmmc_receive_pio
• function au1xmmc_cmd_complete
• function au1xmmc_set_clock
• function au1xmmc_prepare_data
• function au1xmmc_request
• function au1xmmc_reset_controller
• function au1xmmc_set_ios
• function au1xmmc_irq
• function au1xmmc_dbdma_callback
• function au1xmmc_dbdma_init
• function au1xmmc_dbdma_shutdown
• function au1xmmc_enable_sdio_irq
• function au1xmmc_probe
• function au1xmmc_remove
• function au1xmmc_suspend
• function au1xmmc_resume
• function au1xmmc_init
• function au1xmmc_exit
• module init au1xmmc_init

Annotated Snippet

module_init(au1xmmc_init);
module_exit(au1xmmc_exit);

MODULE_AUTHOR("Advanced Micro Devices, Inc");
MODULE_DESCRIPTION("MMC/SD driver for the Alchemy Au1XXX");
MODULE_LICENSE("GPL");
MODULE_ALIAS("platform:au1xxx-mmc");

Annotation

• Immediate include surface: `linux/clk.h`, `linux/module.h`, `linux/init.h`, `linux/platform_device.h`, `linux/mm.h`, `linux/interrupt.h`, `linux/dma-mapping.h`, `linux/scatterlist.h`.
• Detected declarations: `struct au1xmmc_host`, `function has_dbdma`, `function IRQ_ON`, `function FLUSH_FIFO`, `function IRQ_OFF`, `function SEND_STOP`, `function au1xmmc_set_power`, `function au1xmmc_card_inserted`, `function au1xmmc_card_readonly`, `function au1xmmc_finish_request`.
• Atlas domain: Driver Families / drivers/mmc.
• 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.