sound/soc/mediatek/mt6797/mt6797-afe-common.h

File Facts

System

Linux kernel

Corpus path

sound/soc/mediatek/mt6797/mt6797-afe-common.h

Extension

.h

Size

1271 bytes

Lines

60

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/soc.h
• linux/list.h
• linux/regmap.h
• ../common/mtk-base-afe.h

Detected Declarations

• struct clk
• struct mt6797_afe_private

Annotated Snippet

struct mt6797_afe_private {
	struct clk **clk;
};

unsigned int mt6797_general_rate_transform(struct device *dev,
					   unsigned int rate);
unsigned int mt6797_rate_transform(struct device *dev,
				   unsigned int rate, int aud_blk);

/* dai register */
int mt6797_dai_adda_register(struct mtk_base_afe *afe);
int mt6797_dai_pcm_register(struct mtk_base_afe *afe);
int mt6797_dai_hostless_register(struct mtk_base_afe *afe);
#endif

Annotation

• Immediate include surface: `sound/soc.h`, `linux/list.h`, `linux/regmap.h`, `../common/mtk-base-afe.h`.
• Detected declarations: `struct clk`, `struct mt6797_afe_private`.
• 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.