drivers/comedi/drivers/cb_pcidas.c
Source file repositories/reference/linux-study-clean/drivers/comedi/drivers/cb_pcidas.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/comedi/drivers/cb_pcidas.c- Extension
.c- Size
- 43182 bytes
- Lines
- 1500
- 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.
- Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
- Touches IRQ or DMA behavior; this matters for the representative real-device path.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/module.hlinux/delay.hlinux/interrupt.hlinux/comedi/comedi_pci.hlinux/comedi/comedi_8255.hlinux/comedi/comedi_8254.hamcc_s5933.h
Detected Declarations
struct cb_pcidas_boardstruct cb_pcidas_privateenum cb_pcidas_boardidfunction cb_pcidas_ai_eocfunction cb_pcidas_ai_insn_readfunction cb_pcidas_ai_insn_configfunction cb_pcidas_ao_nofifo_insn_writefunction cb_pcidas_ao_fifo_insn_writefunction cb_pcidas_eeprom_readyfunction cb_pcidas_eeprom_insn_readfunction cb_pcidas_calib_writefunction cb_pcidas_caldac_insn_writefunction cb_pcidas_dac08_writefunction cb_pcidas_dac08_insn_writefunction cb_pcidas_trimpot_writefunction cb_pcidas_trimpot_insn_writefunction cb_pcidas_ai_check_chanlistfunction cb_pcidas_ai_cmdtestfunction cb_pcidas_ai_cmdfunction cb_pcidas_ao_check_chanlistfunction cb_pcidas_ao_cmdtestfunction cb_pcidas_ai_cancelfunction cb_pcidas_ao_load_fifofunction cb_pcidas_ao_inttrigfunction cb_pcidas_ao_cmdfunction cb_pcidas_ao_cancelfunction cb_pcidas_ao_interruptfunction cb_pcidas_ai_interruptfunction cb_pcidas_interruptfunction cb_pcidas_auto_attachfunction cb_pcidas_detachfunction cb_pcidas_pci_probe
Annotated Snippet
static struct pci_driver cb_pcidas_pci_driver = {
.name = "cb_pcidas",
.id_table = cb_pcidas_pci_table,
.probe = cb_pcidas_pci_probe,
.remove = comedi_pci_auto_unconfig,
};
module_comedi_pci_driver(cb_pcidas_driver, cb_pcidas_pci_driver);
MODULE_AUTHOR("Comedi https://www.comedi.org");
MODULE_DESCRIPTION("Comedi driver for MeasurementComputing PCI-DAS series");
MODULE_LICENSE("GPL");
Annotation
- Immediate include surface: `linux/module.h`, `linux/delay.h`, `linux/interrupt.h`, `linux/comedi/comedi_pci.h`, `linux/comedi/comedi_8255.h`, `linux/comedi/comedi_8254.h`, `amcc_s5933.h`.
- Detected declarations: `struct cb_pcidas_board`, `struct cb_pcidas_private`, `enum cb_pcidas_boardid`, `function cb_pcidas_ai_eoc`, `function cb_pcidas_ai_insn_read`, `function cb_pcidas_ai_insn_config`, `function cb_pcidas_ao_nofifo_insn_write`, `function cb_pcidas_ao_fifo_insn_write`, `function cb_pcidas_eeprom_ready`, `function cb_pcidas_eeprom_insn_read`.
- Atlas domain: Driver Families / drivers/comedi.
- Implementation status: pattern implementation candidate.
- Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
- IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.
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.