snd_dmaengine_pcm_trigger(9)
π snd_dmaengine_pcm_trigger(9) π
okay so bestie, welcome to the Kernel API Manual β this one's a lil kernel function called snd_dmaengine_pcm_trigger, and honestly? she's giving "small but mighty" energy. let's get into it π
β¨ NAME β¨
snd_dmaengine_pcm_trigger β the dmaengine-based PCM trigger implementation, aka the girl who handles your trigger callbacks π
πΈ SYNOPSIS πΈ
int snd_dmaengine_pcm_trigger (struct snd_pcm_substream *substream , int
cmd );
that's it. that's the whole signature. short queen π
π¦ ARGUMENTS π¦
substreamβ the PCM substream. like, the actual stream we're messing with πcmdβ the trigger command. the vibe check of what you want done β¨
π DESCRIPTION π
so here's the tea β β you can use this function as the PCM trigger callback for your dmaengine-based PCM driver implementations. it's literally built for that. main character energy, no cap π«Ά
β RETURN β
she returns 0 on success bestie π and a negative error code otherwise π (yeah, the classic "not zero = something went wrong" situation, iykyk).
π SEE ALSO π
the kernel file lives right here, iconic:
./sound/core/pcm_dmaengine.c
and the whole friend group π:
snd_hwparams_to_dma_slave_config(9)snd_dmaengine_pcm_set_config_from_dai_data(9)snd_dmaengine_pcm_pointer_no_residue(9)snd_dmaengine_pcm_pointer(9)snd_dmaengine_pcm_request_channel(9)snd_dmaengine_pcm_open(9)snd_dmaengine_pcm_close(9)snd_dmaengine_pcm_close_release_chan(9)snd_dmaengine_pcm_refine_runtime_hwparams(9)
ngl, if your driver's trigger callback was looking for a home, this function ate and left no crumbs π
k byeee, this page came to you straight out of ./sound/core, dated October 2026 β stay slay, keep your error codes negative, and remember: she's in the Kernel API Manual for a reason π§ββοΈπβ¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms