drivers/scsi/zorro_esp.c

File Facts

System

Linux kernel

Corpus path

drivers/scsi/zorro_esp.c

Extension

.c

Size

25326 bytes

Lines

961

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.
• 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/dma-mapping.h
• linux/scatterlist.h
• linux/delay.h
• linux/zorro.h
• linux/slab.h
• linux/pgtable.h
• asm/page.h
• asm/cacheflush.h
• asm/amigahw.h
• asm/amigaints.h
• scsi/scsi_host.h
• scsi/scsi_transport_spi.h
• scsi/scsi_device.h
• scsi/scsi_tcq.h
• esp_scsi.h

Detected Declarations

• struct blz1230_dma_registers
• struct blz1230II_dma_registers
• struct blz2060_dma_registers
• struct cyber_dma_registers
• struct cyberII_dma_registers
• struct fastlane_dma_registers
• struct zorro_esp_priv
• struct zorro_driver_data
• function zorro_esp_write8
• function zorro_esp_read8
• function zorro_esp_irq_pending
• function cyber_esp_irq_pending
• function fastlane_esp_irq_pending
• function zorro_esp_dma_length_limit
• function fastlane_esp_dma_length_limit
• function zorro_esp_reset_dma
• function zorro_esp_send_blz1230_dma_cmd
• function zorro_esp_send_blz1230II_dma_cmd
• function zorro_esp_send_blz2060_dma_cmd
• function zorro_esp_send_cyber_dma_cmd
• function zorro_esp_send_cyberII_dma_cmd
• function zorro_esp_send_fastlane_dma_cmd
• function zorro_esp_dma_error
• function zorro_esp_probe
• function zorro_esp_remove
• function zorro_esp_scsi_init
• function zorro_esp_scsi_exit
• module init zorro_esp_scsi_init

Annotated Snippet

module_init(zorro_esp_scsi_init);
module_exit(zorro_esp_scsi_exit);

Annotation

• Immediate include surface: `linux/module.h`, `linux/init.h`, `linux/interrupt.h`, `linux/dma-mapping.h`, `linux/scatterlist.h`, `linux/delay.h`, `linux/zorro.h`, `linux/slab.h`.
• Detected declarations: `struct blz1230_dma_registers`, `struct blz1230II_dma_registers`, `struct blz2060_dma_registers`, `struct cyber_dma_registers`, `struct cyberII_dma_registers`, `struct fastlane_dma_registers`, `struct zorro_esp_priv`, `struct zorro_driver_data`, `function zorro_esp_write8`, `function zorro_esp_read8`.
• Atlas domain: Driver Families / drivers/scsi.
• Implementation status: integration implementation candidate.
• 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.