sound/soc/ti/sdma-pcm.c

File Facts

System

Linux kernel

Corpus path

sound/soc/ti/sdma-pcm.c

Extension

.c

Size

1959 bytes

Lines

72

Domain

Driver Families

Bucket

sound/soc

Inferred role

Driver Families: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/device.h
• linux/module.h
• sound/core.h
• sound/pcm.h
• sound/pcm_params.h
• sound/soc.h
• sound/dmaengine_pcm.h
• sdma-pcm.h

Detected Declarations

• function sdma_pcm_platform_register
• export sdma_pcm_platform_register

Annotated Snippet

if (!txdmachan) {
			txdmachan = rxdmachan;
			rxdmachan = NULL;
		}
	}

	config->chan_names[0] = txdmachan;
	config->chan_names[1] = rxdmachan;

	return devm_snd_dmaengine_pcm_register(dev, config, flags);
}
EXPORT_SYMBOL_GPL(sdma_pcm_platform_register);

MODULE_AUTHOR("Peter Ujfalusi <peter.ujfalusi@ti.com>");
MODULE_DESCRIPTION("sDMA PCM ASoC platform driver");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/device.h`, `linux/module.h`, `sound/core.h`, `sound/pcm.h`, `sound/pcm_params.h`, `sound/soc.h`, `sound/dmaengine_pcm.h`, `sdma-pcm.h`.
• Detected declarations: `function sdma_pcm_platform_register`, `export sdma_pcm_platform_register`.
• Atlas domain: Driver Families / sound/soc.
• Implementation status: integration 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.