drivers/memstick/host/tifm_ms.c

File Facts

System

Linux kernel

Corpus path

drivers/memstick/host/tifm_ms.c

Extension

.c

Size

16816 bytes

Lines

683

Domain

Driver Families

Bucket

drivers/memstick

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

Dependency Surface

• linux/tifm.h
• linux/memstick.h
• linux/highmem.h
• linux/scatterlist.h
• linux/log2.h
• linux/module.h
• asm/io.h

Detected Declarations

• struct tifm_ms
• function tifm_ms_read_data
• function tifm_ms_write_data
• function tifm_ms_transfer_data
• function tifm_ms_issue_cmd
• function tifm_ms_complete_cmd
• function tifm_ms_check_status
• function tifm_ms_data_event
• function tifm_ms_card_event
• function tifm_ms_req_tasklet
• function tifm_ms_dummy_submit
• function tifm_ms_submit_req
• function tifm_ms_set_param
• function tifm_ms_abort
• function tifm_ms_probe
• function tifm_ms_remove
• function tifm_ms_suspend
• function tifm_ms_resume
• function tifm_ms_init
• function tifm_ms_exit
• module init tifm_ms_init

Annotated Snippet

module_init(tifm_ms_init);
module_exit(tifm_ms_exit);

Annotation

• Immediate include surface: `linux/tifm.h`, `linux/memstick.h`, `linux/highmem.h`, `linux/scatterlist.h`, `linux/log2.h`, `linux/module.h`, `asm/io.h`.
• Detected declarations: `struct tifm_ms`, `function tifm_ms_read_data`, `function tifm_ms_write_data`, `function tifm_ms_transfer_data`, `function tifm_ms_issue_cmd`, `function tifm_ms_complete_cmd`, `function tifm_ms_check_status`, `function tifm_ms_data_event`, `function tifm_ms_card_event`, `function tifm_ms_req_tasklet`.
• Atlas domain: Driver Families / drivers/memstick.
• 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.