drivers/scsi/53c700.c

File Facts

System

Linux kernel

Corpus path

drivers/scsi/53c700.c

Extension

.c

Size

68359 bytes

Lines

2119

Domain

Driver Families

Bucket

drivers/scsi

Inferred role

Driver Families: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• 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/types.h
• linux/string.h
• linux/slab.h
• linux/ioport.h
• linux/delay.h
• linux/spinlock.h
• linux/completion.h
• linux/init.h
• linux/proc_fs.h
• linux/blkdev.h
• linux/module.h
• linux/interrupt.h
• linux/device.h
• linux/pgtable.h
• asm/dma.h
• asm/io.h
• asm/byteorder.h
• scsi/scsi.h
• scsi/scsi_cmnd.h
• scsi/scsi_dbg.h
• scsi/scsi_eh.h
• scsi/scsi_host.h
• scsi/scsi_tcq.h
• scsi/scsi_transport.h
• scsi/scsi_transport_spi.h
• 53c700.h
• 53c700_d.h

Detected Declarations

• function NCR_700_offset_period_to_sxfer
• function NCR_700_get_SXFER
• function virt_to_dma
• function dma_sync_to_dev
• function dma_sync_from_dev
• function NCR_700_detect
• function NCR_700_release
• function NCR_700_identify
• function NCR_700_data_residual
• function sbcl_to_string
• function bitmap_to_number
• function find_empty_slot
• function free_slot
• function and
• function NCR_700_unmap
• function NCR_700_scsi_done
• function NCR_700_internal_bus_reset
• function NCR_700_chip_setup
• function NCR_700_chip_reset
• function process_message
• function process_script_interrupt
• function scsi_for_each_sg
• function necessary
• function NCR_700_clear_fifo
• function NCR_700_flush_fifo
• function NCR_700_start_command
• function NCR_700_intr
• function NCR_700_queuecommand_lck
• function scsi_for_each_sg
• function DEF_SCSI_QCMD
• function NCR_700_host_reset
• function NCR_700_set_period
• function NCR_700_set_offset
• function NCR_700_sdev_init
• function NCR_700_sdev_configure
• function NCR_700_sdev_destroy
• function NCR_700_change_queue_depth
• function NCR_700_show_active_tags
• function NCR_700_init
• function NCR_700_exit
• module init NCR_700_init
• export NCR_700_detect
• export NCR_700_release
• export NCR_700_intr

Annotated Snippet

module_init(NCR_700_init);
module_exit(NCR_700_exit);

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/types.h`, `linux/string.h`, `linux/slab.h`, `linux/ioport.h`, `linux/delay.h`, `linux/spinlock.h`, `linux/completion.h`.
• Detected declarations: `function NCR_700_offset_period_to_sxfer`, `function NCR_700_get_SXFER`, `function virt_to_dma`, `function dma_sync_to_dev`, `function dma_sync_from_dev`, `function NCR_700_detect`, `function NCR_700_release`, `function NCR_700_identify`, `function NCR_700_data_residual`, `function sbcl_to_string`.
• Atlas domain: Driver Families / drivers/scsi.
• Implementation status: integration 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.