drivers/memstick/host/r592.c

File Facts

System

Linux kernel

Corpus path

drivers/memstick/host/r592.c

Extension

.c

Size

21802 bytes

Lines

895

Domain

Driver Families

Bucket

drivers/memstick

Inferred role

Driver Families: operation-table or driver-model contract

Status

pattern 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.
• Defines an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• 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/kernel.h
• linux/module.h
• linux/freezer.h
• linux/jiffies.h
• linux/interrupt.h
• linux/pci.h
• linux/pci_ids.h
• linux/delay.h
• linux/slab.h
• linux/kthread.h
• linux/sched.h
• linux/highmem.h
• asm/byteorder.h
• linux/swab.h
• r592.h

Detected Declarations

• function r592_read_reg
• function r592_write_reg
• function r592_read_reg_raw_be
• function r592_write_reg_raw_be
• function r592_set_reg_mask
• function r592_clear_reg_mask
• function r592_wait_status
• function r592_enable_device
• function r592_set_mode
• function r592_host_reset
• function r592_clear_interrupts
• function r592_test_io_error
• function r592_test_fifo_empty
• function r592_start_dma
• function r592_stop_dma
• function r592_check_dma
• function r592_transfer_fifo_dma
• function r592_write_fifo_pio
• function r592_flush_fifo_write
• function r592_read_fifo_pio
• function r592_transfer_fifo_pio
• function r592_execute_tpc
• function r592_process_thread
• function r592_update_card_detect
• function r592_detect_timer
• function r592_irq
• function r592_set_param
• function r592_submit_req
• function r592_probe
• function r592_remove
• function r592_suspend
• function r592_resume

Annotated Snippet

static struct pci_driver r592_pci_driver = {
	.name		= DRV_NAME,
	.id_table	= r592_pci_id_tbl,
	.probe		= r592_probe,
	.remove		= r592_remove,
	.driver.pm	= &r592_pm_ops,
};

module_pci_driver(r592_pci_driver);

module_param_named(enable_dma, r592_enable_dma, bool, S_IRUGO);
MODULE_PARM_DESC(enable_dma, "Enable usage of the DMA (default)");
module_param(debug, int, S_IRUGO | S_IWUSR);
MODULE_PARM_DESC(debug, "Debug level (0-3)");

MODULE_LICENSE("GPL");
MODULE_AUTHOR("Maxim Levitsky <maximlevitsky@gmail.com>");
MODULE_DESCRIPTION("Ricoh R5C592 Memstick/Memstick PRO card reader driver");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/freezer.h`, `linux/jiffies.h`, `linux/interrupt.h`, `linux/pci.h`, `linux/pci_ids.h`, `linux/delay.h`.
• Detected declarations: `function r592_read_reg`, `function r592_write_reg`, `function r592_read_reg_raw_be`, `function r592_write_reg_raw_be`, `function r592_set_reg_mask`, `function r592_clear_reg_mask`, `function r592_wait_status`, `function r592_enable_device`, `function r592_set_mode`, `function r592_host_reset`.
• Atlas domain: Driver Families / drivers/memstick.
• Implementation status: pattern 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.