drivers/scsi/stex.c

File Facts

System

Linux kernel

Corpus path

drivers/scsi/stex.c

Extension

.c

Size

49315 bytes

Lines

2031

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/init.h
• linux/errno.h
• linux/kernel.h
• linux/delay.h
• linux/slab.h
• linux/time.h
• linux/pci.h
• linux/blkdev.h
• linux/interrupt.h
• linux/types.h
• linux/module.h
• linux/spinlock.h
• linux/ktime.h
• linux/reboot.h
• asm/io.h
• asm/irq.h
• asm/byteorder.h
• scsi/scsi.h
• scsi/scsi_device.h
• scsi/scsi_cmnd.h
• scsi/scsi_host.h
• scsi/scsi_tcq.h
• scsi/scsi_dbg.h
• scsi/scsi_eh.h

Detected Declarations

• struct st_sgitem
• struct st_ss_sgitem
• struct st_sgtable
• struct st_msg_header
• struct handshake_frame
• struct req_msg
• struct status_msg
• struct ver_info
• struct st_frame
• struct st_drvver
• struct st_ccb
• struct st_hba
• struct st_card_info
• function stex_invalid_field
• function stex_map_sg
• function scsi_for_each_sg
• function stex_ss_map_sg
• function scsi_for_each_sg
• function stex_controller_info
• function stex_send_cmd
• function stex_ss_send_cmd
• function return_abnormal_state
• function stex_sdev_configure
• function stex_queuecommand_lck
• function DEF_SCSI_QCMD
• function stex_copy_data
• function stex_check_cmd
• function stex_mu_intr
• function stex_intr
• function stex_ss_mu_intr
• function stex_ss_intr
• function stex_common_handshake
• function stex_ss_handshake
• function stex_handshake
• function stex_abort
• function stex_hard_reset
• function stex_yos_reset
• function stex_ss_reset
• function stex_p3_reset
• function stex_do_reset
• function stex_reset
• function stex_reset_work
• function stex_biosparam
• function stex_request_irq
• function stex_free_irq
• function stex_probe
• function stex_hba_stop
• function stex_hba_free

Annotated Snippet

static struct pci_driver stex_pci_driver = {
	.name		= DRV_NAME,
	.id_table	= stex_pci_tbl,
	.probe		= stex_probe,
	.remove		= stex_remove,
	.shutdown	= stex_shutdown,
	.suspend	= stex_suspend,
	.resume		= stex_resume,
};

static int __init stex_init(void)
{
	printk(KERN_INFO DRV_NAME
		": Promise SuperTrak EX Driver version: %s\n",
		 ST_DRIVER_VERSION);

	return pci_register_driver(&stex_pci_driver);
}

static void __exit stex_exit(void)
{
	pci_unregister_driver(&stex_pci_driver);
}

module_init(stex_init);
module_exit(stex_exit);

Annotation

• Immediate include surface: `linux/init.h`, `linux/errno.h`, `linux/kernel.h`, `linux/delay.h`, `linux/slab.h`, `linux/time.h`, `linux/pci.h`, `linux/blkdev.h`.
• Detected declarations: `struct st_sgitem`, `struct st_ss_sgitem`, `struct st_sgtable`, `struct st_msg_header`, `struct handshake_frame`, `struct req_msg`, `struct status_msg`, `struct ver_info`, `struct st_frame`, `struct st_drvver`.
• 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.