exynos_drm_...t_caps_ioctl(9)

exynos_drm_...t_caps_ioctl(9) 🎀

okay so welcome to this page from the Kernel API Manual, bestie. The manual name is literally exynos_drm_...t_caps_ioctl(9) — yes, the title is serving ellipsis realness. Let’s get into it. 💅

---

💖 NAME 💖

exynos_drm_ipp_get_caps_ioctl — get ipp module capabilities and formats.

✨ SYNOPSIS ✨

int exynos_drm_ipp_get_caps_ioctl (struct drm_device *dev , void *data ,
       struct drm_file *file_priv );

🎀 ARGUMENTS 🎀

Three arguments, three besties, no skipping:

• dev — DRM device. The DRM device is right there, being a device.
• data — ioctl data. The ioctl data, doing its data thing.
• file_priv — DRM file info. The DRM file info, holding it down for the file side of the function.

🦋 DESCRIPTION 🦋

okay so what this does is construct a structure describing the ipp module capabilities. It’s giving “tell me what this ipp module can do” energy — and this function builds the structure that says it. 💫

It’s called by the user via ioctl. So yes, the user hits the ioctl door, and this is the function waiting on the other side. No cap. 🫶

🌸 RETURN 🌸

Zero on success — slay. Negative errno on failure — not slay, but at least you know what’s up. Periodt. ✨

💅 SEE ALSO 💅

Kernel file: ./drivers/gpu/drm/exynos/exynos_drm_ipp.c — that’s the source, bestie. Go read it, iykyk. 📖

The whole friend group:

• exynos_drm_ipp_register(9)
• exynos_drm_ipp_unregister(9)
• exynos_drm_ipp_get_res_ioctl(9)
• exynos_drm_ipp_get_limits_ioctl(9)
• exynos_drm_ipp_task_done(9)
• exynos_drm_ipp_commit_ioctl(9)

---

xoxo, your kernel bestie 💖 — sourced from ./drivers/gpu/drm/exynos, dated October 2026, and forever filed under exynos_drm_...t_caps_ioctl(9). Bye bestie! 🫶