drivers/comedi/drivers/dt282x.c
Source file repositories/reference/linux-study-clean/drivers/comedi/drivers/dt282x.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/comedi/drivers/dt282x.c- Extension
.c- Size
- 30212 bytes
- Lines
- 1176
- Domain
- Driver Families
- Bucket
- drivers/comedi
- Inferred role
- Driver Families: implementation source
- Status
- source 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.
- 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/gfp.hlinux/interrupt.hlinux/io.hlinux/comedi/comedidev.hlinux/comedi/comedi_isadma.h
Detected Declarations
struct dt282x_boardstruct dt282x_privatefunction dt282x_prep_ai_dmafunction dt282x_prep_ao_dmafunction dt282x_disable_dmafunction dt282x_ns_to_timerfunction dt282x_mungefunction dt282x_ao_setup_dmafunction dt282x_ao_dma_interruptfunction dt282x_ai_dma_interruptfunction dt282x_interruptfunction dt282x_load_changainfunction dt282x_ai_timeoutfunction dt282x_ai_insn_readfunction dt282x_ai_cmdtestfunction dt282x_ai_cmdfunction dt282x_ai_cancelfunction dt282x_ao_insn_writefunction dt282x_ao_cmdtestfunction dt282x_ao_inttrigfunction dt282x_ao_cmdfunction dt282x_ao_cancelfunction dt282x_dio_insn_bitsfunction dt282x_dio_insn_configfunction dt282x_alloc_dmafunction dt282x_free_dmafunction dt282x_initializefunction dt282x_attachfunction dt282x_detach
Annotated Snippet
struct dt282x_board {
const char *name;
unsigned int ai_maxdata;
int adchan_se;
int adchan_di;
int ai_speed;
int ispgl;
int dachan;
unsigned int ao_maxdata;
};
static const struct dt282x_board boardtypes[] = {
{
.name = "dt2821",
.ai_maxdata = 0x0fff,
.adchan_se = 16,
.adchan_di = 8,
.ai_speed = 20000,
.dachan = 2,
.ao_maxdata = 0x0fff,
}, {
.name = "dt2821-f",
.ai_maxdata = 0x0fff,
.adchan_se = 16,
.adchan_di = 8,
.ai_speed = 6500,
.dachan = 2,
.ao_maxdata = 0x0fff,
}, {
.name = "dt2821-g",
.ai_maxdata = 0x0fff,
.adchan_se = 16,
.adchan_di = 8,
.ai_speed = 4000,
.dachan = 2,
.ao_maxdata = 0x0fff,
}, {
.name = "dt2823",
.ai_maxdata = 0xffff,
.adchan_di = 4,
.ai_speed = 10000,
.dachan = 2,
.ao_maxdata = 0xffff,
}, {
.name = "dt2824-pgh",
.ai_maxdata = 0x0fff,
.adchan_se = 16,
.adchan_di = 8,
.ai_speed = 20000,
}, {
.name = "dt2824-pgl",
.ai_maxdata = 0x0fff,
.adchan_se = 16,
.adchan_di = 8,
.ai_speed = 20000,
.ispgl = 1,
}, {
.name = "dt2825",
.ai_maxdata = 0x0fff,
.adchan_se = 16,
.adchan_di = 8,
.ai_speed = 20000,
.ispgl = 1,
.dachan = 2,
.ao_maxdata = 0x0fff,
}, {
.name = "dt2827",
.ai_maxdata = 0xffff,
.adchan_di = 4,
.ai_speed = 10000,
.dachan = 2,
.ao_maxdata = 0x0fff,
}, {
.name = "dt2828",
.ai_maxdata = 0x0fff,
.adchan_se = 4,
.ai_speed = 10000,
.dachan = 2,
.ao_maxdata = 0x0fff,
}, {
.name = "dt2829",
.ai_maxdata = 0xffff,
.adchan_se = 8,
.ai_speed = 33250,
.dachan = 2,
.ao_maxdata = 0xffff,
}, {
.name = "dt21-ez",
.ai_maxdata = 0x0fff,
.adchan_se = 16,
Annotation
- Immediate include surface: `linux/module.h`, `linux/delay.h`, `linux/gfp.h`, `linux/interrupt.h`, `linux/io.h`, `linux/comedi/comedidev.h`, `linux/comedi/comedi_isadma.h`.
- Detected declarations: `struct dt282x_board`, `struct dt282x_private`, `function dt282x_prep_ai_dma`, `function dt282x_prep_ao_dma`, `function dt282x_disable_dma`, `function dt282x_ns_to_timer`, `function dt282x_munge`, `function dt282x_ao_setup_dma`, `function dt282x_ao_dma_interrupt`, `function dt282x_ai_dma_interrupt`.
- Atlas domain: Driver Families / drivers/comedi.
- Implementation status: source implementation candidate.
- 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.