drivers/mmc/core/core.c

File Facts

System

Linux kernel

Corpus path

drivers/mmc/core/core.c

Extension

.c

Size

62149 bytes

Lines

2430

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

Dependency Surface

• linux/module.h
• linux/init.h
• linux/interrupt.h
• linux/completion.h
• linux/device.h
• linux/delay.h
• linux/pagemap.h
• linux/err.h
• linux/leds.h
• linux/scatterlist.h
• linux/log2.h
• linux/pm_runtime.h
• linux/suspend.h
• linux/fault-inject.h
• linux/random.h
• linux/slab.h
• linux/of.h
• linux/mmc/card.h
• linux/mmc/host.h
• linux/mmc/mmc.h
• linux/mmc/sd.h
• linux/mmc/slot-gpio.h
• trace/events/mmc.h
• core.h
• card.h
• crypto.h
• bus.h
• host.h
• sdio_bus.h
• pwrseq.h
• mmc_ops.h
• sd_ops.h

Detected Declarations

• function mmc_schedule_delayed_work
• function mmc_should_fail_request
• function mmc_should_fail_request
• function mmc_command_done
• function mmc_request_done
• function __mmc_start_request
• function mmc_mrq_pr_debug
• function mmc_mrq_prep
• function mmc_start_request
• function mmc_wait_done
• function mmc_wait_ongoing_tfr_cmd
• function __mmc_start_req
• function mmc_wait_for_req_done
• function mmc_cqe_start_req
• function mmc_cqe_request_done
• function mmc_cqe_post_req
• function mmc_cqe_request_done
• function mmc_is_req_done
• function mmc_wait_for_req_done
• function mmc_wait_for_cmd
• function mmc_set_data_timeout
• function mmc_ctx_matches
• function mmc_ctx_set_claimer
• function __mmc_claim_host
• function mmc_release_host
• function mmc_get_card
• function mmc_put_card
• function mmc_set_ios
• function mmc_set_chip_select
• function mmc_set_clock
• function mmc_execute_tuning
• function mode
• function mmc_set_bus_width
• function mmc_set_initial_state
• function mmc_vdd_to_ocrbitnum
• function mmc_vddrange_to_ocrmask
• function mmc_of_get_func_num
• function for_each_child_of_node
• function mmc_select_voltage
• function mmc_set_signal_voltage
• function mmc_set_initial_signal_voltage
• function mmc_host_set_uhs_voltage
• function mmc_set_uhs_voltage
• function mmc_set_timing
• function mmc_set_driver_type
• function mmc_select_drive_strength
• function mmc_power_up
• function mmc_power_off

Annotated Snippet

subsys_initcall(mmc_init);
module_exit(mmc_exit);

MODULE_DESCRIPTION("MMC core driver");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/module.h`, `linux/init.h`, `linux/interrupt.h`, `linux/completion.h`, `linux/device.h`, `linux/delay.h`, `linux/pagemap.h`, `linux/err.h`.
• Detected declarations: `function mmc_schedule_delayed_work`, `function mmc_should_fail_request`, `function mmc_should_fail_request`, `function mmc_command_done`, `function mmc_request_done`, `function __mmc_start_request`, `function mmc_mrq_pr_debug`, `function mmc_mrq_prep`, `function mmc_start_request`, `function mmc_wait_done`.
• 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.

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.