sound/soc/codecs/rt5659.h

File Facts

System

Linux kernel

Corpus path

sound/soc/codecs/rt5659.h

Extension

.h

Size

64833 bytes

Lines

1822

Domain

Driver Families

Bucket

sound/soc

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

• sound/rt5659.h

Detected Declarations

• struct rt5659_pll_code
• struct rt5659_priv

Annotated Snippet

struct rt5659_pll_code {
	bool m_bp;
	int m_code;
	int n_code;
	int k_code;
};

struct rt5659_priv {
	struct snd_soc_component *component;
	struct rt5659_platform_data pdata;
	struct regmap *regmap;
	struct gpio_desc *gpiod_ldo1_en;
	struct gpio_desc *gpiod_reset;
	struct snd_soc_jack *hs_jack;
	struct delayed_work jack_detect_work;
	struct clk *mclk;

	int sysclk;
	int sysclk_src;
	int lrck[RT5659_AIFS];
	int bclk[RT5659_AIFS];
	int master[RT5659_AIFS];
	int v_id;

	int pll_src;
	int pll_in;
	int pll_out;

	int jack_type;
	bool hda_hp_plugged;
	bool hda_mic_plugged;
};

int rt5659_set_jack_detect(struct snd_soc_component *component,
	struct snd_soc_jack *hs_jack);

#endif /* __RT5659_H__ */

Annotation

• Immediate include surface: `sound/rt5659.h`.
• Detected declarations: `struct rt5659_pll_code`, `struct rt5659_priv`.
• Atlas domain: Driver Families / sound/soc.
• 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.