drivers/comedi/drivers/ke_counter.c

File Facts

System

Linux kernel

Corpus path

drivers/comedi/drivers/ke_counter.c

Extension

.c

Size

5656 bytes

Lines

232

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

Detected Declarations

• function Copyright
• function ke_counter_insn_read
• function ke_counter_reset
• function ke_counter_insn_config
• function ke_counter_do_insn_bits
• function ke_counter_auto_attach
• function ke_counter_pci_probe

Annotated Snippet

static struct pci_driver ke_counter_pci_driver = {
	.name		= "ke_counter",
	.id_table	= ke_counter_pci_table,
	.probe		= ke_counter_pci_probe,
	.remove		= comedi_pci_auto_unconfig,
};
module_comedi_pci_driver(ke_counter_driver, ke_counter_pci_driver);

MODULE_AUTHOR("Comedi https://www.comedi.org");
MODULE_DESCRIPTION("Comedi driver for Kolter Electronic Counter Card");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/module.h`, `linux/comedi/comedi_pci.h`.
• Detected declarations: `function Copyright`, `function ke_counter_insn_read`, `function ke_counter_reset`, `function ke_counter_insn_config`, `function ke_counter_do_insn_bits`, `function ke_counter_auto_attach`, `function ke_counter_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.