drm_ioctl_t(9)

💅 drm_ioctl_t(9) — Kernel API Manual ✨

🎀 NAME 🎀

drm_ioctl_t — DRM ioctl function type. That's the name, that's the vibe, and it's lowkey iconic.

✨ SYNOPSIS ✨

Here's the exact typedef, bestie — copy it character for character:

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

🫶 ARGUMENTS 🫶

• dev — DRM device inode. That's the device inode you're working with, periodt.
• data — private pointer of the ioctl call. It's the private pointer for this ioctl call.
• file_priv — DRM file this ioctl was made on. Basically the DRM file that this ioctl was made on.

🔥 DESCRIPTION 🔥

Okay so this is the DRM ioctl typedef. The important lore is that drm_ioctl has already copied data into kernel-space — the original manpage literally spells it alrady, and we respect the typo 😭 — and it will also copy it back, depending upon the read/write settings in the ioctl command code. So the data-copying situation is already handled on the drm_ioctl side; your typedef just has to show up and slay.

Fr fr, keep this detail: the copy into kernel-space has already happened, and the copy back depends upon the read/write settings in the ioctl command code. That's the caveat, bestie.

🌈 SEE ALSO 🌈

Go read these next, iykyk:

• Kernel file ./include/drm/drm_ioctl.h
• drm_ioctl_compat_t(9)
• enum drm_ioctl_flags(9)
• struct drm_ioctl_desc(9)
• DRM_IOCTL_DEF_DRV(9)

Sign-off tea 🫖: this page lives under ./include/drm, is dated October 2026, and is serving drm_ioctl_t(9) energy. Bye bestie, go ioctl responsibly 💖✨