drivers/scsi/hptiop.c
Source file repositories/reference/linux-study-clean/drivers/scsi/hptiop.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/scsi/hptiop.c- Extension
.c- Size
- 46355 bytes
- Lines
- 1700
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/module.hlinux/types.hlinux/string.hlinux/kernel.hlinux/pci.hlinux/interrupt.hlinux/errno.hlinux/delay.hlinux/timer.hlinux/spinlock.hlinux/gfp.hlinux/uaccess.hasm/io.hasm/div64.hscsi/scsi_cmnd.hscsi/scsi_device.hscsi/scsi.hscsi/scsi_tcq.hscsi/scsi_host.hhptiop.h
Detected Declarations
function iop_wait_ready_itlfunction iop_wait_ready_mvfunction iop_wait_ready_mvfreyfunction hptiop_request_callback_itlfunction hptiop_drain_outbound_queue_itlfunction iop_intr_itlfunction mv_outbound_readfunction mv_inbound_writefunction hptiop_request_callback_mvfunction iop_intr_mvfunction hptiop_request_callback_mvfreyfunction iop_intr_mvfreyfunction iop_send_sync_request_itlfunction iop_send_sync_request_mvfunction iop_send_sync_request_mvfreyfunction hptiop_post_msg_itlfunction hptiop_post_msg_mvfunction hptiop_post_msg_mvfreyfunction iop_send_sync_msgfunction iop_get_config_itlfunction iop_get_config_mvfunction iop_get_config_mvfreyfunction iop_set_config_itlfunction iop_set_config_mvfunction iop_set_config_mvfreyfunction hptiop_enable_intr_itlfunction hptiop_enable_intr_mvfunction hptiop_enable_intr_mvfreyfunction hptiop_initialize_iopfunction hptiop_map_pci_bar_itlfunction hptiop_unmap_pci_bar_itlfunction hptiop_map_pci_bar_mvfunction hptiop_map_pci_bar_mvfreyfunction hptiop_unmap_pci_bar_mvfunction hptiop_unmap_pci_bar_mvfreyfunction hptiop_message_callbackfunction free_reqfunction hptiop_finish_scsi_reqfunction hptiop_host_request_callback_itlfunction hptiop_iop_request_callback_itlfunction hptiop_intrfunction hptiop_buildsglfunction scsi_for_each_sgfunction hptiop_post_req_itlfunction hptiop_post_req_mvfunction hptiop_post_req_mvfreyfunction hptiop_reset_comm_itlfunction hptiop_reset_comm_mv
Annotated Snippet
static struct pci_driver hptiop_pci_driver = {
.name = driver_name,
.id_table = hptiop_id_table,
.probe = hptiop_probe,
.remove = hptiop_remove,
.shutdown = hptiop_shutdown,
};
static int __init hptiop_module_init(void)
{
printk(KERN_INFO "%s %s\n", driver_name_long, driver_ver);
return pci_register_driver(&hptiop_pci_driver);
}
static void __exit hptiop_module_exit(void)
{
pci_unregister_driver(&hptiop_pci_driver);
}
module_init(hptiop_module_init);
module_exit(hptiop_module_exit);
MODULE_LICENSE("GPL");
Annotation
- Immediate include surface: `linux/module.h`, `linux/types.h`, `linux/string.h`, `linux/kernel.h`, `linux/pci.h`, `linux/interrupt.h`, `linux/errno.h`, `linux/delay.h`.
- Detected declarations: `function iop_wait_ready_itl`, `function iop_wait_ready_mv`, `function iop_wait_ready_mvfrey`, `function hptiop_request_callback_itl`, `function hptiop_drain_outbound_queue_itl`, `function iop_intr_itl`, `function mv_outbound_read`, `function mv_inbound_write`, `function hptiop_request_callback_mv`, `function iop_intr_mv`.
- 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.