drivers/scsi/fdomain_pci.c

File Facts

System

Linux kernel

Corpus path

drivers/scsi/fdomain_pci.c

Extension

.c

Size

1444 bytes

Lines

69

Domain

Driver Families

Bucket

drivers/scsi

Inferred role

Driver Families: operation-table or driver-model contract

Status

pattern 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.
• Defines an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/module.h
• linux/pci.h
• fdomain.h

Detected Declarations

• function fdomain_pci_probe
• function fdomain_pci_remove

Annotated Snippet

static struct pci_driver fdomain_pci_driver = {
	.name		= "fdomain_pci",
	.id_table	= fdomain_pci_table,
	.probe		= fdomain_pci_probe,
	.remove		= fdomain_pci_remove,
	.driver.pm	= FDOMAIN_PM_OPS,
};

module_pci_driver(fdomain_pci_driver);

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

Annotation

• Immediate include surface: `linux/module.h`, `linux/pci.h`, `fdomain.h`.
• Detected declarations: `function fdomain_pci_probe`, `function fdomain_pci_remove`.
• Atlas domain: Driver Families / drivers/scsi.
• Implementation status: pattern 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.