pvr_dev_quer...ncements_get(9)

💅 pvr_dev_quer...ncements_get(9) — from the Kernel API Manual, bestie ✨

okay so you're in the kernel API manual and you found pvr_dev_quer...ncements_get(9) — that's the page. welcome, pull up a chair 🎀

---

🌸 NAME 🌸

pvr_dev_query_enhancements_get — it unpacks the array of enhancements at the address you gave it in a struct drm_pvr_dev_query_enhancements, or it just tells you how much space you need for that whole situation. two jobs, one function, main character energy 👑

---

✨ SYNOPSIS ✨

int pvr_dev_query_enhancements_get (struct pvr_device *pvr_dev , struct
drm_pvr_ioctl_dev_query_args *args );

like, that's the whole vibe. two args, one int back 🫶

---

🦋 ARGUMENTS 🦋

• pvr_dev — the device pointer, your lil handle on the actual hardware situation 💖
• args — [IN] device query arguments, and inside them lives a pointer to a userspace struct drm_pvr_dev_query_enhancements. that pointer is the whole point of the operation, no cap

---

💜 DESCRIPTION 💜

so here's the tea 🍵 — read these branches carefully, they're doing a lot:

• if the query object pointer is NULL, then the size field gets updated with the expected size of the query object. that's your "how big should this be" mode, iconic
• if the userspace pointer in the query object is NULL, or the count is short — then no data is copied. literally none. don't come for the data, there is no data 😭
• the count field will be updated to whichever count actually got copied — or, if either pointer is NULL, it gets updated to the count that would have been copied 👀
• and the size field in the query object gets updated to the size copied

that's it, that's the whole dance. size in, size out, and the count reporting on what did or didn't happen 💫

---

🔥 RETURN 🔥

• 0 on success — or also 0 if size/count is being requested with a NULL pointer, because that's a valid ask, bestie ✔️
• -EINVAL if args contained non-zero reserved fields — like, those fields are reserved, respect them 🙈
• -E2BIG if the indicated length of the allocation is less than what's required to contain the copied data. your buffer is too small, that's the whole problem 💀
• -EFAULT if local memory could not be copied to userspace. the copy did not slay, it failed 😔

---

🌈 SEE ALSO 🌈

the whole friend group, in order, exactly as listed:

• Kernel file ./drivers/gpu/drm/imagination/pvr_drv.c — PowerVR (Series 6 and later) and IMG Graphics Driver(9)
• pvr_ioctl_create_bo(9)
• pvr_ioctl_get_bo_mmap_offset(9)
• pvr_dev_query_gpu_info_get(9)
• pvr_dev_query_runtime_info_get(9)
• pvr_dev_query_quirks_get(9)
• pvr_ioctl_dev_query(9)
• pvr_ioctl_create_context(9)
• pvr_ioctl_destroy_context(9)
• pvr_ioctl_create_free_list(9)
• pvr_ioctl_destroy_free_list(9)
• pvr_ioctl_create_hwrt_dataset(9)
• pvr_ioctl_destroy_hwrt_dataset(9)
• pvr_ioctl_create_vm_context(9)
• pvr_ioctl_destroy_vm_context(9)
• pvr_ioctl_vm_map(9)
• pvr_ioctl_vm_unmap(9)
• pvr_drm_driver_open(9)
• pvr_drm_driver_postclose(9)

that's nineteen friends plus the driver file. go read them all, i'll wait 🧚

---

and that's the page!! source situation: ./drivers/gpu/drm/imagination, dated October 2026 — mwah, love that for us, bye bestie 💅💖🎀