drivers/mmc/host/vub300.c

File Facts

System

Linux kernel

Corpus path

drivers/mmc/host/vub300.c

Extension

.c

Size

73198 bytes

Lines

2482

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.
• 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/errno.h
• linux/init.h
• linux/slab.h
• linux/module.h
• linux/kref.h
• linux/uaccess.h
• linux/usb.h
• linux/mutex.h
• linux/mmc/host.h
• linux/mmc/card.h
• linux/mmc/sdio_func.h
• linux/mmc/sdio_ids.h
• linux/workqueue.h
• linux/ctype.h
• linux/firmware.h
• linux/scatterlist.h

Detected Declarations

• struct host_controller_info
• struct sd_command_header
• struct sd_irqpoll_header
• struct sd_common_header
• struct sd_response_header
• struct sd_status_header
• struct sd_error_header
• struct sd_interrupt_header
• struct offload_registers_access
• struct sd_offloaded_interrupt
• struct sd_register_header
• struct sd_offloaded_piggyback
• struct sdio_register
• struct vub300_mmc_host
• struct offload_interrupt_function_register
• enum SD_RESPONSE_TYPE
• function interface_to_InterfaceNumber
• function vub300_delete
• function vub300_queue_cmnd_work
• function vub300_queue_poll_work
• function vub300_queue_dead_work
• function irqpoll_res_completed
• function irqpoll_out_completed
• function send_irqpoll
• function new_system_port_status
• function __add_offloaded_reg_to_fifo
• function add_offloaded_reg
• function check_vub300_port_status
• function __vub300_irqpoll_response
• function __do_poll
• function vub300_pollwork_thread
• function vub300_deadwork_thread
• function vub300_inactivity_timer_expired
• function vub300_response_error
• function command_res_completed
• function command_out_completed
• function snoop_block_size_and_bus_width
• function send_command
• function usb_kill_urb
• function roundup_to_multiple_of_64
• function __download_offload_pseudocode
• function download_offload_pseudocode
• function vub300_usb_bulk_msg_completion
• function vub300_usb_bulk_msg
• function __command_read_data
• function __command_write_data
• function __vub300_command_response
• function construct_request_response

Annotated Snippet

module_init(vub300_init);
module_exit(vub300_exit);

MODULE_AUTHOR("Tony Olech <tony.olech@elandigitalsystems.com>");
MODULE_DESCRIPTION("VUB300 USB to SD/MMC/SDIO adapter driver");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/errno.h`, `linux/init.h`, `linux/slab.h`, `linux/module.h`, `linux/kref.h`, `linux/uaccess.h`, `linux/usb.h`.
• Detected declarations: `struct host_controller_info`, `struct sd_command_header`, `struct sd_irqpoll_header`, `struct sd_common_header`, `struct sd_response_header`, `struct sd_status_header`, `struct sd_error_header`, `struct sd_interrupt_header`, `struct offload_registers_access`, `struct sd_offloaded_interrupt`.
• 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.