drivers/scsi/sym53c8xx_2/sym_glue.c
Source file repositories/reference/linux-study-clean/drivers/scsi/sym53c8xx_2/sym_glue.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/scsi/sym53c8xx_2/sym_glue.c- Extension
.c- Size
- 54634 bytes
- Lines
- 2112
- 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/ctype.hlinux/init.hlinux/module.hlinux/moduleparam.hlinux/spinlock.hscsi/scsi.hscsi/scsi_tcq.hscsi/scsi_device.hscsi/scsi_transport.hsym_glue.hsym_nvram.h
Detected Declarations
struct sym_ucmdstruct sym_usrcmdfunction sym2_setup_paramsfunction sym_xpt_donefunction sym_xpt_async_bus_resetfunction sym_xerr_cam_statusfunction sym_set_cam_result_errorfunction sym_scatterfunction scsi_for_each_sgfunction sym_queue_commandfunction sym_setup_cdbfunction sym_setup_data_and_startfunction sym_timerfunction sym_log_bus_errorfunction sym53c8xx_queue_command_lckfunction DEF_SCSI_QCMDfunction sym53c8xx_timerfunction threadfunction sym53c8xx_eh_target_reset_handlerfunction FOR_EACH_QUEUED_ELEMENTfunction sym53c8xx_eh_bus_reset_handlerfunction sym53c8xx_eh_host_reset_handlerfunction sym_tune_dev_queuingfunction sym53c8xx_sdev_initfunction sym53c8xx_sdev_configurefunction sym53c8xx_sdev_destroyfunction infofunction sym_exec_user_commandfunction sym_skip_spacesfunction get_int_argfunction is_keywordfunction sym_user_commandfunction sym_show_infofunction sym_iomap_devicefunction sym_free_resourcesfunction sym_get_nvramfunction sym_get_nvramfunction sym_check_raidfunction sym_set_workaroundsfunction sym_iomap_devicefunction IDfunction sym_detachfunction sym2_probefunction sym2_removefunction sym2_io_error_detectedfunction sym2_io_slot_dumpfunction sym_set_workaroundsfunction sym2_io_slot_reset
Annotated Snippet
static struct pci_driver sym2_driver = {
.name = NAME53C8XX,
.id_table = sym2_id_table,
.probe = sym2_probe,
.remove = sym2_remove,
.err_handler = &sym2_err_handler,
};
static int __init sym2_init(void)
{
int error;
sym2_setup_params();
sym2_transport_template = spi_attach_transport(&sym2_transport_functions);
if (!sym2_transport_template)
return -ENODEV;
error = pci_register_driver(&sym2_driver);
if (error)
spi_release_transport(sym2_transport_template);
return error;
}
static void __exit sym2_exit(void)
{
pci_unregister_driver(&sym2_driver);
spi_release_transport(sym2_transport_template);
}
module_init(sym2_init);
module_exit(sym2_exit);
Annotation
- Immediate include surface: `linux/ctype.h`, `linux/init.h`, `linux/module.h`, `linux/moduleparam.h`, `linux/spinlock.h`, `scsi/scsi.h`, `scsi/scsi_tcq.h`, `scsi/scsi_device.h`.
- Detected declarations: `struct sym_ucmd`, `struct sym_usrcmd`, `function sym2_setup_params`, `function sym_xpt_done`, `function sym_xpt_async_bus_reset`, `function sym_xerr_cam_status`, `function sym_set_cam_result_error`, `function sym_scatter`, `function scsi_for_each_sg`, `function sym_queue_command`.
- 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.