include/sound/hda_i915.h

File Facts

System

Linux kernel

Corpus path

include/sound/hda_i915.h

Extension

.h

Size

589 bytes

Lines

28

Domain

Driver Families

Bucket

include/sound

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

• hda_component.h

Detected Declarations

• function snd_hdac_i915_set_bclk
• function snd_hdac_i915_exit

Annotated Snippet

#ifndef __SOUND_HDA_I915_H
#define __SOUND_HDA_I915_H

#include "hda_component.h"

#ifdef CONFIG_SND_HDA_I915
void snd_hdac_i915_set_bclk(struct hdac_bus *bus);
int snd_hdac_i915_init(struct hdac_bus *bus);
#else
static inline void snd_hdac_i915_set_bclk(struct hdac_bus *bus)
{
}
static inline int snd_hdac_i915_init(struct hdac_bus *bus)
{
	return -ENODEV;
}
#endif
static inline int snd_hdac_i915_exit(struct hdac_bus *bus)
{
	return snd_hdac_acomp_exit(bus);
}

#endif /* __SOUND_HDA_I915_H */

Annotation

• Immediate include surface: `hda_component.h`.
• Detected declarations: `function snd_hdac_i915_set_bclk`, `function snd_hdac_i915_exit`.
• Atlas domain: Driver Families / include/sound.
• 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.