drivers/scsi/lasi700.c
Source file repositories/reference/linux-study-clean/drivers/scsi/lasi700.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/scsi/lasi700.c- Extension
.c- Size
- 4062 bytes
- Lines
- 172
- 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/kernel.hlinux/module.hlinux/init.hlinux/types.hlinux/stat.hlinux/mm.hlinux/blkdev.hlinux/ioport.hlinux/dma-mapping.hlinux/slab.hasm/page.hasm/irq.hasm/hardware.hasm/parisc-device.hasm/delay.hscsi/scsi_host.hscsi/scsi_device.hscsi/scsi_transport.hscsi/scsi_transport_spi.h53c700.h
Detected Declarations
function lasi700_probefunction lasi700_driver_removefunction lasi700_initfunction lasi700_exitmodule init lasi700_init
Annotated Snippet
module_init(lasi700_init);
module_exit(lasi700_exit);Annotation
- Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/init.h`, `linux/types.h`, `linux/stat.h`, `linux/mm.h`, `linux/blkdev.h`, `linux/ioport.h`.
- Detected declarations: `function lasi700_probe`, `function lasi700_driver_remove`, `function lasi700_init`, `function lasi700_exit`, `module init lasi700_init`.
- 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.