drivers/scsi/BusLogic.c

File Facts

System

Linux kernel

Corpus path

drivers/scsi/BusLogic.c

Extension

.c

Size

124672 bytes

Lines

3738

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/module.h
• linux/init.h
• linux/interrupt.h
• linux/types.h
• linux/blkdev.h
• linux/delay.h
• linux/ioport.h
• linux/mm.h
• linux/stat.h
• linux/pci.h
• linux/spinlock.h
• linux/jiffies.h
• linux/dma-mapping.h
• linux/slab.h
• linux/msdos_partition.h
• scsi/scsicam.h
• asm/dma.h
• asm/io.h
• scsi/scsi.h
• scsi/scsi_cmnd.h
• scsi/scsi_device.h
• scsi/scsi_host.h
• scsi/scsi_tcq.h
• BusLogic.h
• FlashPoint.c

Detected Declarations

• function blogic_announce_drvr
• function Blocks
• function blogic_create_initccbs
• function blogic_destroy_ccbs
• function blogic_create_addlccbs
• function blogic_dealloc_ccb
• function blogic_cmd
• function blogic_sort_probeinfo
• function blogic_init_mm_probeinfo
• function blogic_init_fp_probeinfo
• function blogic_init_probeinfo_list
• function blogic_failure
• function blogic_probe
• function blogic_hwreset
• function blogic_checkadapter
• function blogic_rdconfig
• function blogic_reportconfig
• function blogic_flashpoint_type
• function blogic_getres
• function blogic_relres
• function blogic_initadapter
• function blogic_inquiry
• function blogic_inithoststruct
• function blogic_sdev_configure
• function blogic_init
• function blogic_deladapter
• function blogic_qcompleted_ccb
• function blogic_resultcode
• function blogic_inbox_to_ccb
• function blogic_scan_inbox
• function blogic_process_ccbs
• function Adapter
• function CmdQue
• function blogic_inthandler
• function blogic_write_outbox
• function blogic_hostreset
• function blogic_qcmd_lck
• function scsi_for_each_sg
• function DEF_SCSI_QCMD
• function blogic_resetadapter
• function blogic_diskparam
• function translations
• function blogic_write_info
• function blogic_show_info
• function blogic_msg
• function blogic_parse
• function blogic_parseopts
• function blogic_parse

Annotated Snippet

module_init(blogic_init);
module_exit(blogic_exit);

Annotation

• Immediate include surface: `linux/module.h`, `linux/init.h`, `linux/interrupt.h`, `linux/types.h`, `linux/blkdev.h`, `linux/delay.h`, `linux/ioport.h`, `linux/mm.h`.
• Detected declarations: `function blogic_announce_drvr`, `function Blocks`, `function blogic_create_initccbs`, `function blogic_destroy_ccbs`, `function blogic_create_addlccbs`, `function blogic_dealloc_ccb`, `function blogic_cmd`, `function blogic_sort_probeinfo`, `function blogic_init_mm_probeinfo`, `function blogic_init_fp_probeinfo`.
• 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.