drivers/scsi/dmx3191d.c

File Facts

System

Linux kernel

Corpus path

drivers/scsi/dmx3191d.c

Extension

.c

Size

3709 bytes

Lines

149

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/init.h
• linux/ioport.h
• linux/kernel.h
• linux/module.h
• linux/pci.h
• linux/interrupt.h
• asm/io.h
• scsi/scsi_host.h
• NCR5380.h
• NCR5380.c

Detected Declarations

• function dmx3191d_probe_one
• function dmx3191d_remove_one

Annotated Snippet

static struct pci_driver dmx3191d_pci_driver = {
	.name		= DMX3191D_DRIVER_NAME,
	.id_table	= dmx3191d_pci_tbl,
	.probe		= dmx3191d_probe_one,
	.remove		= dmx3191d_remove_one,
};

module_pci_driver(dmx3191d_pci_driver);

MODULE_AUTHOR("Massimo Piccioni <dafastidio@libero.it>");
MODULE_DESCRIPTION("Domex DMX3191D SCSI driver");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/init.h`, `linux/ioport.h`, `linux/kernel.h`, `linux/module.h`, `linux/pci.h`, `linux/interrupt.h`, `asm/io.h`, `scsi/scsi_host.h`.
• Detected declarations: `function dmx3191d_probe_one`, `function dmx3191d_remove_one`.
• 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.