sound/soc/amd/renoir/rn_acp3x.h
Source file repositories/reference/linux-study-clean/sound/soc/amd/renoir/rn_acp3x.h
File Facts
- System
- Linux kernel
- Corpus path
sound/soc/amd/renoir/rn_acp3x.h- Extension
.h- Size
- 2354 bytes
- Lines
- 94
- 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
rn_chip_offset_byte.h
Detected Declarations
struct pdm_dev_datastruct pdm_stream_instancefunction rn_readlfunction rn_writel
Annotated Snippet
struct pdm_dev_data {
u32 pdm_irq;
void __iomem *acp_base;
struct snd_pcm_substream *capture_stream;
};
struct pdm_stream_instance {
u16 num_pages;
u16 channels;
dma_addr_t dma_addr;
u64 bytescount;
void __iomem *acp_base;
};
union acp_pdm_dma_count {
struct {
u32 low;
u32 high;
} bcount;
u64 bytescount;
};
static inline u32 rn_readl(void __iomem *base_addr)
{
return readl(base_addr - ACP_PHY_BASE_ADDRESS);
}
static inline void rn_writel(u32 val, void __iomem *base_addr)
{
writel(val, base_addr - ACP_PHY_BASE_ADDRESS);
}
/* Machine configuration */
int snd_amd_acp_find_config(struct pci_dev *pci);
Annotation
- Immediate include surface: `rn_chip_offset_byte.h`.
- Detected declarations: `struct pdm_dev_data`, `struct pdm_stream_instance`, `function rn_readl`, `function rn_writel`.
- 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.