ipc4_probes_init(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ipc4_probes_init (9) β€” from the Kernel API Manual, bestie ✨

okay so you found your way to ipc4_probes_init and honestly? slay. this one lives in the Kernel API Manual section 9, and it's the little function that gets data probing up and running. let's get into it πŸŽ€


✨ NAME ✨

ipc4_probes_init β€” initialize data probing πŸ¦‹


✨ SYNOPSIS ✨

int ipc4_probes_init (struct sof_client_dev *cdev , u32 stream_tag ,
size_t buffer_size );

like, that's the whole signature. three args, one int coming back at you. no cap πŸ’–


✨ ARGUMENTS ✨

  • cdev β€” the SOF client device 🫢 that's your device, your main character
  • stream_tag β€” the extractor stream tag ✨ yes, this matters a lot, keep reading
  • buffer_size β€” the DMA buffer size to set for the extractor 🌸

✨ RETURN ✨

0 on success, and a negative error code on error 😭 that's it, that's the deal. if you get 0 you ate. if you get something negative, vibe check failed, go look at your errors πŸ’€


✨ DESCRIPTION ✨

okay so here's the lore πŸ‘‘

The host chooses whether extraction is supported or not by providing a valid stream_tag to the DSP. Once specified, the stream described by that tag will be tied to the DSP for extraction for the entire lifetime of probe. literally the whole time. it's giving commitment πŸ’œ

Probing is initialized only once, and each INIT request must be matched by a DEINIT call. πŸ™ˆ so don't just spam INIT, bestie β€” you gotta pair it up. one INIT, one DEINIT. periodt.

⚠️ no fr fr: probing is initialized only once, and every INIT request must be matched by a DEINIT call. don't leave your DEINIT hanging, that's not the vibe πŸ’…

✨ SEE ALSO ✨

like, read the whole squad, they're all iconic πŸ‘‘


anyway that's the page!! this one ships out of ./sound/soc/sof and the date on it is October 2026 🌈 so yeah, mark your calendar bestie, mwah πŸ’–πŸŽ€πŸ«Ά

πŸ“¦ where this page comes from