sound/core/seq/oss/seq_oss_writeq.h

File Facts

System

Linux kernel

Corpus path

sound/core/seq/oss/seq_oss_writeq.h

Extension

.h

Size

928 bytes

Lines

38

Domain

Driver Families

Bucket

sound/core

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

• seq_oss_device.h

Detected Declarations

• struct seq_oss_writeq

Annotated Snippet

struct seq_oss_writeq {
	struct seq_oss_devinfo *dp;
	int maxlen;
	abstime_t sync_time;
	int sync_event_put;
	wait_queue_head_t sync_sleep;
	spinlock_t sync_lock;
};


/*
 * seq_oss_writeq.c
 */
struct seq_oss_writeq *snd_seq_oss_writeq_new(struct seq_oss_devinfo *dp, int maxlen);
void snd_seq_oss_writeq_delete(struct seq_oss_writeq *q);
void snd_seq_oss_writeq_clear(struct seq_oss_writeq *q);
int snd_seq_oss_writeq_sync(struct seq_oss_writeq *q);
void snd_seq_oss_writeq_wakeup(struct seq_oss_writeq *q, abstime_t time);
int snd_seq_oss_writeq_get_free_size(struct seq_oss_writeq *q);
void snd_seq_oss_writeq_set_output(struct seq_oss_writeq *q, int size);


#endif

Annotation

• Immediate include surface: `seq_oss_device.h`.
• Detected declarations: `struct seq_oss_writeq`.
• Atlas domain: Driver Families / sound/core.
• 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.