drivers/scsi/dc395x.c

File Facts

System

Linux kernel

Corpus path

drivers/scsi/dc395x.c

Extension

.c

Size

113835 bytes

Lines

4063

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/module.h
• linux/moduleparam.h
• linux/delay.h
• linux/ctype.h
• linux/blkdev.h
• linux/interrupt.h
• linux/init.h
• linux/spinlock.h
• linux/pci.h
• linux/list.h
• linux/vmalloc.h
• linux/slab.h
• asm/io.h
• scsi/scsi.h
• scsi/scsi_cmnd.h
• scsi/scsi_device.h
• scsi/scsi_host.h
• scsi/scsi_transport_spi.h
• dc395x.h

Detected Declarations

• struct SGentry
• struct NVRamTarget
• struct NvRamType
• struct ScsiReqBlk
• struct DeviceCtlBlk
• struct AdapterCtlBlk
• struct ParameterData
• function set_safe_settings
• function fix_settings
• function eeprom_index_to_delay
• function delay_to_eeprom_index
• function eeprom_override
• function list_size
• function list_for_each_entry
• function free_tag
• function waiting_set_timer
• function waiting_process_next
• function waiting_timeout
• function send_srb
• function build_srb
• function scsi_for_each_sg
• function adapter
• function DEF_SCSI_QCMD
• function reset_dev_param
• function list_for_each_entry
• function __dc395x_eh_bus_reset
• function dc395x_eh_bus_reset
• function dc395x_eh_abort
• function build_sdtr
• function build_wdtr
• function selto_timer
• function selection_timeout_missed
• function start_scsi
• function enable_msgout_abort
• function dc395x_handle_interrupt
• function dc395x_interrupt
• function msgout_phase0
• function msgout_phase1
• function command_phase0
• function command_phase1
• function sg_update_list
• function byte
• function cleanup_after_transfer
• function data_out_phase0
• function data_out_phase1
• function data_in_phase0
• function that
• function data_in_phase1

Annotated Snippet

static struct pci_driver dc395x_driver = {
	.name           = DC395X_NAME,
	.id_table       = dc395x_pci_table,
	.probe          = dc395x_init_one,
	.remove         = dc395x_remove_one,
};
module_pci_driver(dc395x_driver);

MODULE_AUTHOR("C.L. Huang / Erich Chen / Kurt Garloff");
MODULE_DESCRIPTION("SCSI host adapter driver for Tekram TRM-S1040 based adapters: Tekram DC395 and DC315 series");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/module.h`, `linux/moduleparam.h`, `linux/delay.h`, `linux/ctype.h`, `linux/blkdev.h`, `linux/interrupt.h`, `linux/init.h`, `linux/spinlock.h`.
• Detected declarations: `struct SGentry`, `struct NVRamTarget`, `struct NvRamType`, `struct ScsiReqBlk`, `struct DeviceCtlBlk`, `struct AdapterCtlBlk`, `struct ParameterData`, `function set_safe_settings`, `function fix_settings`, `function eeprom_index_to_delay`.
• 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.