include/sound/wm8960.h

File Facts

System

Linux kernel

Corpus path

include/sound/wm8960.h

Extension

.h

Size

888 bytes

Lines

39

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

• No C-style include directives detected by the generator.

Detected Declarations

• struct wm8960_data

Annotated Snippet

struct wm8960_data {
	bool capless;  /* Headphone outputs configured in capless mode */

	bool shared_lrclk;  /* DAC and ADC LRCLKs are wired together */

	/*
	 * Setup for headphone detection
	 *
	 * hp_cfg[0]: HPSEL[1:0] of R48 (Additional Control 4)
	 * hp_cfg[1]: {HPSWEN:HPSWPOL} of R24 (Additional Control 2).
	 * hp_cfg[2]: {TOCLKSEL:TOEN} of R23 (Additional Control 1).
	 */
	u32 hp_cfg[3];

	/*
	 * Setup for gpio configuration
	 *
	 * gpio_cfg[0]: ALRCGPIO of R9 (Audio interface)
	 * gpio_cfg[1]: {GPIOPOL:GPIOSEL[2:0]} of R48 (Additional Control 4).
	 */
	u32 gpio_cfg[2];
};

#endif

Annotation

• Detected declarations: `struct wm8960_data`.
• 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.