ipu_image_convert(9)

💅 ipu_image_convert(9) — the Kernel API Manual, bestie edition

okay so this is a page from the Kernel API Manual, and I'm gonna walk you through ipu_image_convert like we're texting at 2am. it's giving "asynchronous image conversion request" energy and honestly? iconic. 🦋

---

✨ NAME ✨

ipu_image_convert — asynchronous image conversion request

like, you ask for an image conversion, and it doesn't block you. main character scheduling behavior, no cap. 👑

---

🎀 SYNOPSIS 🎀

struct ipu_image_convert_run * ipu_image_convert (struct ipu_soc *ipu ,
enum ipu_ic_task ic_task , struct ipu_image *in , struct ipu_image *out
, enum ipu_rotate_mode rot_mode , ipu_image_convert_cb_t complete , void
*complete_context );

that's the whole signature, copied exactly, do not touch, we stan a verbatim prototype. 💅

---

🌸 ARGUMENTS 🌸

• ipu — the IPU handle you're using for the conversion. it's the vibe check of "which hardware are we even talking to".
• ic_task — the IC task to use for the conversion. pick your fighter. ⭐
• in — input image format.
• out — output image format. (yes, in goes in, out goes out, we love a consistent queen.)
• rot_mode — rotation mode. spin it, tilt it, whatever the enum says. 🌈
• complete — run completion callback. this is the "text me when you're done" function. 🫶
• complete_context — a context pointer for the completion callback. so your callback knows whose group chat it's replying to.

---

💖 DESCRIPTION 💖

so here's the tea: you're requesting a single image conversion. the function returns the run that has been queued — like handing in your order and getting the receipt immediately. 🔥

a conversion context is automatically created for you, and it's available at run->ctx. so thoughtful, so generous, we love a function that does the admin for us. ✨

and just like with ipu_image_convert_prepare, the input/output formats and the rotation mode must already meet IPU restrictions before you even show up. no last-minute glow-ups at this stage, bestie — the requirements are the requirements. 🙈

on a successful return, the caller can queue more run requests if needed, using that prepared context in run->ctx. so you can keep the party going. 🎀

but — and this is the important part — the caller is responsible for unpreparing the context when no more conversion requests are needed. that's your mess, your cleanup. nobody else is gonna do it for you. 🧹💀

---

⭐ RETURN ⭐

on success you get a pointer to the created struct ipu_image_convert_run that has been queued. 🎉

on error you get an ERR_PTR(errno). so like... check it. always check it. IS_ERR() is your friend, iykyk. 😭

---

🦋 SEE ALSO 🦋

• Kernel file ./include/video/imx-ipu-image-convert.h
• struct ipu_image_convert_run(9)
• ipu_image_convert_cb_t(9)
• ipu_image_convert_adjust(9)
• ipu_image_convert_verify(9)
• ipu_image_convert_prepare(9)
• ipu_image_convert_unprepare(9)
• ipu_image_convert_queue(9)
• ipu_image_convert_abort(9)

that's the whole friend group, go say hi. 🫶

---

okay and finally the sign-off: this page lives out of ./include/video, and it's dated October 2026, and yes it's still ipu_image_convert(9) — same girl, same manual. slay, bye! 💜✨🎀