drivers/comedi/drivers/adv_pci1720.c

File Facts

System

Linux kernel

Corpus path

drivers/comedi/drivers/adv_pci1720.c

Extension

.c

Size

5398 bytes

Lines

186

Domain

Driver Families

Bucket

drivers/comedi

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/delay.h
• linux/comedi/comedi_pci.h

Detected Declarations

• function pci1720_ao_insn_write
• function pci1720_di_insn_bits
• function pci1720_auto_attach
• function adv_pci1720_pci_probe

Annotated Snippet

static struct pci_driver adv_pci1720_pci_driver = {
	.name		= "adv_pci1720",
	.id_table	= adv_pci1720_pci_table,
	.probe		= adv_pci1720_pci_probe,
	.remove		= comedi_pci_auto_unconfig,
};
module_comedi_pci_driver(adv_pci1720_driver, adv_pci1720_pci_driver);

MODULE_AUTHOR("H Hartley Sweeten <hsweeten@visionengravers.com>");
MODULE_DESCRIPTION("Comedi driver for Advantech PCI-1720 Analog Output board");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/module.h`, `linux/delay.h`, `linux/comedi/comedi_pci.h`.
• Detected declarations: `function pci1720_ao_insn_write`, `function pci1720_di_insn_bits`, `function pci1720_auto_attach`, `function adv_pci1720_pci_probe`.
• Atlas domain: Driver Families / drivers/comedi.
• 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.