exynos_drm_i...et_res_ioctl(9)
β¨ NAME β¨
exynos_drm_ipp_get_res_ioctl β bestie, this one's job is literally to enumerate all ipp modules π
(also hi, this is a page from the Kernel API Manual β yes, that manual, we're fancy now π)
β¨ SYNOPSIS β¨
int exynos_drm_ipp_get_res_ioctl (struct drm_device *dev , void *data ,
struct drm_file *file_priv );
β¨ ARGUMENTS β¨
devβ the DRM device, the main character of this whole situation π«Άdataβ the ioctl data, just vibing in therefile_privβ DRM file info, iykyk π₯
β¨ DESCRIPTION β¨
Okay so the whole serve here is: it constructs a list of ipp ids. That's the moment. That's the assignment. π¦
And how does this iconic function get called? By the user, via ioctl. Periodt. π
β¨ RETURN β¨
- Zero on success πΈ (slay, no cap)
- Negative errno on failure π (it's giving β¨errorβ¨, we don't love it)
ngl, if you get a negative errno back, that's your sign something went sideways β fr fr, negative errno = failure, no exceptions.
β¨ SEE ALSO β¨
- Kernel file
./drivers/gpu/drm/exynos/exynos_drm_ipp.cπ exynos_drm_ipp_register(9)β obsessedexynos_drm_ipp_unregister(9)exynos_drm_ipp_get_caps_ioctl(9)exynos_drm_ipp_get_limits_ioctl(9)exynos_drm_ipp_task_done(9)exynos_drm_ipp_commit_ioctl(9)
all of these are the friend group, go say hi π
okay bestie that's the whole page π§ this little gem lives in ./drivers/gpu/drm/exynos, it's dated October 2026, and the manual lists it as exynos_drm_i...et_res_ioctl(9) β go forth and enumerate those ipp modules, you're gonna eat πβ¨
π¦ 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