drivers/scsi/mvumi.c

File Facts

System

Linux kernel

Corpus path

drivers/scsi/mvumi.c

Extension

.c

Size

70030 bytes

Lines

2633

Domain

Driver Families

Bucket

drivers/scsi

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.
• 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/module.h
• linux/moduleparam.h
• linux/init.h
• linux/device.h
• linux/pci.h
• linux/list.h
• linux/spinlock.h
• linux/interrupt.h
• linux/delay.h
• linux/ktime.h
• linux/blkdev.h
• linux/io.h
• scsi/scsi.h
• scsi/scsi_cmnd.h
• scsi/scsi_device.h
• scsi/scsi_host.h
• scsi/scsi_transport.h
• scsi/scsi_eh.h
• linux/uaccess.h
• linux/kthread.h
• mvumi.h

Detected Declarations

• function tag_init
• function tag_get_one
• function tag_release_one
• function tag_is_empty
• function mvumi_unmap_pci_addr
• function mvumi_map_pci_addr
• function mvumi_release_mem_resource
• function list_for_each_entry_safe
• function mvumi_make_sgl
• function mvumi_internal_cmd_sgl
• function mvumi_delete_internal_cmd
• function mvumi_return_cmd
• function mvumi_free_cmds
• function mvumi_alloc_cmds
• function mvumi_check_ib_list_9143
• function mvumi_check_ib_list_9580
• function mvumi_get_ib_list_entry
• function mvumi_send_ib_list_entry
• function mvumi_check_ob_frame
• function mvumi_check_ob_list_9143
• function mvumi_check_ob_list_9580
• function mvumi_receive_ob_list_entry
• function mvumi_reset
• function mvumi_wait_for_outstanding
• function mvumi_wait_for_fw
• function mvumi_backup_bar_addr
• function mvumi_restore_bar_addr
• function mvumi_pci_set_master
• function mvumi_reset_host_9580
• function mvumi_reset_host_9143
• function mvumi_host_reset
• function mvumi_issue_blocked_cmd
• function mvumi_release_fw
• function mvumi_flush_cache
• function mvumi_calculate_checksum
• function mvumi_hs_build_page
• function mvumi_init_data
• function mvumi_hs_process_page
• function mvumi_handshake
• function mvumi_handshake_event
• function mvumi_check_handshake
• function mvumi_start
• function mvumi_complete_cmd
• function mvumi_complete_internal_cmd
• function mvumi_show_event
• function mvumi_handle_hotplug
• function mvumi_inquiry
• function mvumi_detach_devices

Annotated Snippet

static struct pci_driver mvumi_pci_driver = {

	.name = MV_DRIVER_NAME,
	.id_table = mvumi_pci_table,
	.probe = mvumi_probe_one,
	.remove = mvumi_detach_one,
	.shutdown = mvumi_shutdown,
	.driver.pm = &mvumi_pm_ops,
};

module_pci_driver(mvumi_pci_driver);

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/moduleparam.h`, `linux/init.h`, `linux/device.h`, `linux/pci.h`, `linux/list.h`, `linux/spinlock.h`.
• Detected declarations: `function tag_init`, `function tag_get_one`, `function tag_release_one`, `function tag_is_empty`, `function mvumi_unmap_pci_addr`, `function mvumi_map_pci_addr`, `function mvumi_release_mem_resource`, `function list_for_each_entry_safe`, `function mvumi_make_sgl`, `function mvumi_internal_cmd_sgl`.
• Atlas domain: Driver Families / drivers/scsi.
• 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.