drivers/comedi/drivers/amplc_dio200.h

File Facts

System

Linux kernel

Corpus path

drivers/comedi/drivers/amplc_dio200.h

Extension

.h

Size

1316 bytes

Lines

47

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/types.h

Detected Declarations

• struct comedi_device
• struct dio200_board
• enum dio200_sdtype

Annotated Snippet

struct dio200_board {
	const char *name;
	unsigned char mainbar;
	unsigned short n_subdevs;	/* number of subdevices */
	unsigned char sdtype[DIO200_MAX_SUBDEVS];	/* enum dio200_sdtype */
	unsigned char sdinfo[DIO200_MAX_SUBDEVS];	/* depends on sdtype */
	unsigned int has_int_sce:1;	/* has interrupt enable/status reg */
	unsigned int has_clk_gat_sce:1;	/* has clock/gate selection registers */
	unsigned int is_pcie:1;			/* has enhanced features */
};

int amplc_dio200_common_attach(struct comedi_device *dev, unsigned int irq,
			       unsigned long req_irq_flags);

/* Used by initialization of PCIe boards. */
void amplc_dio200_set_enhance(struct comedi_device *dev, unsigned char val);

#endif

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct comedi_device`, `struct dio200_board`, `enum dio200_sdtype`.
• Atlas domain: Driver Families / drivers/comedi.
• Implementation status: source 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.