drivers/comedi/drivers/das08.h

File Facts

System

Linux kernel

Corpus path

drivers/comedi/drivers/das08.h

Extension

.h

Size

1192 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 das08_board_struct
• struct das08_private_struct
• enum das08_ai_encoding
• enum das08_lrange

Annotated Snippet

struct das08_board_struct {
	const char *name;
	bool is_jr;		/* true for 'JR' boards */
	unsigned int ai_nbits;
	enum das08_lrange ai_pg;
	enum das08_ai_encoding ai_encoding;
	unsigned int ao_nbits;
	unsigned int di_nchan;
	unsigned int do_nchan;
	unsigned int i8255_offset;
	unsigned int i8254_offset;
	unsigned int iosize;	/* number of ioports used */
};

struct das08_private_struct {
	/* bits for do/mux register on boards without separate do register */
	unsigned int do_mux_bits;
	const unsigned int *pg_gainlist;
};

int das08_common_attach(struct comedi_device *dev, unsigned long iobase);

#endif /* _DAS08_H */

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct comedi_device`, `struct das08_board_struct`, `struct das08_private_struct`, `enum das08_ai_encoding`, `enum das08_lrange`.
• 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.