drivers/scsi/fdomain_isa.c

File Facts

System

Linux kernel

Corpus path

drivers/scsi/fdomain_isa.c

Extension

.c

Size

6747 bytes

Lines

220

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.h
• linux/io.h
• linux/isa.h
• scsi/scsi_host.h
• fdomain.h

Detected Declarations

• function fdomain_isa_match
• function fdomain_isa_param_match
• function fdomain_isa_remove
• function fdomain_isa_init
• function fdomain_isa_exit
• module init fdomain_isa_init

Annotated Snippet

module_init(fdomain_isa_init);
module_exit(fdomain_isa_exit);

MODULE_AUTHOR("Ondrej Zary, Rickard E. Faith");
MODULE_DESCRIPTION("Future Domain TMC-16x0 ISA SCSI driver");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/module.h`, `linux/io.h`, `linux/isa.h`, `scsi/scsi_host.h`, `fdomain.h`.
• Detected declarations: `function fdomain_isa_match`, `function fdomain_isa_param_match`, `function fdomain_isa_remove`, `function fdomain_isa_init`, `function fdomain_isa_exit`, `module init fdomain_isa_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.