drivers/scsi/arm/oak.c
Source file repositories/reference/linux-study-clean/drivers/scsi/arm/oak.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/scsi/arm/oak.c- Extension
.c- Size
- 4468 bytes
- Lines
- 214
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/module.hlinux/ioport.hlinux/blkdev.hlinux/init.hasm/ecard.hasm/io.hscsi/scsi_host.h../NCR5380.h../NCR5380.c
Detected Declarations
function oakscsi_pwritefunction oakscsi_preadfunction oakscsi_probefunction oakscsi_removefunction oakscsi_initfunction oakscsi_exitmodule init oakscsi_init
Annotated Snippet
module_init(oakscsi_init);
module_exit(oakscsi_exit);
MODULE_AUTHOR("Russell King");
MODULE_DESCRIPTION("Oak SCSI driver");
MODULE_LICENSE("GPL");Annotation
- Immediate include surface: `linux/module.h`, `linux/ioport.h`, `linux/blkdev.h`, `linux/init.h`, `asm/ecard.h`, `asm/io.h`, `scsi/scsi_host.h`, `../NCR5380.h`.
- Detected declarations: `function oakscsi_pwrite`, `function oakscsi_pread`, `function oakscsi_probe`, `function oakscsi_remove`, `function oakscsi_init`, `function oakscsi_exit`, `module init oakscsi_init`.
- Atlas domain: Driver Families / drivers/scsi.
- Implementation status: integration implementation candidate.
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.