STRUCT DRM_IVPU_PARAM(9)

💅 struct drm_ivpu_param(9) — the kernel API manual, but make it make sense

okay bestie, so this is a page from the Kernel API Manual about struct drm_ivpu_param, and honestly? it's giving "small struct, big responsibilities." let's get into it 🎀

---

✨ NAME ✨

struct drm_ivpu_param — Get/Set VPU parameters. that's it, that's the whole vibe. you use this thing to get (and set) parameters on the VPU. 🦋

---

🌸 SYNOPSIS 🌸

here's the struct, exactly as it lives, no cap:

struct drm_ivpu_param {
    __u32 param;
    __u32 index;
    __u64 value;
 };

three fields. tiny. iconic. 👑

---

💖 Members 💖

the param field 🧚

okay so param is where you say which parameter you want, and the supported ones are a whole little list. every single one, coming right up:

• DRM_IVPU_PARAM_DEVICE_ID — the PCI Device ID of the VPU device. read-only, so look but don't touch 💅
• DRM_IVPU_PARAM_DEVICE_REVISION — the VPU device revision. also read-only.
• DRM_IVPU_PARAM_PLATFORM_TYPE — returns DRM_IVPU_PLATFORM_TYPE_SILICON when you're on real hardware, or the device-specific platform type when you're executing on a simulator or emulator. read-only, bestie, it's just reporting the tea 🫖
• DRM_IVPU_PARAM_CORE_CLOCK_RATE — the maximum frequency of the NPU data processing unit clock. read-only ⏰
• DRM_IVPU_PARAM_NUM_CONTEXTS — the maximum number of simultaneously existing contexts. read-only.
• DRM_IVPU_PARAM_CONTEXT_BASE_ADDRESS — the lowest VPU virtual address available in the current context. read-only.
• DRM_IVPU_PARAM_CONTEXT_ID — the current context ID, which is always greater than 0. read-only, and lowkey the main character of context identifiers ✨
• DRM_IVPU_PARAM_FW_API_VERSION — the Firmware API version array. read-only.
• DRM_IVPU_PARAM_ENGINE_HEARTBEAT — a heartbeat value from an engine, read-only. and this is the fun one: the Engine ID (i.e. DRM_IVPU_ENGINE_COMPUTE) is given via index. 👀
• DRM_IVPU_PARAM_UNIQUE_INFERENCE_ID — the device-unique inference ID. read-only. it's literally one of a kind, iykyk 💜
• DRM_IVPU_PARAM_TILE_CONFIG — the VPU tile configuration. read-only. (yes there are two spaces in the original, we respect the formatting 🎀)
• DRM_IVPU_PARAM_SKU — the VPU SKU ID. read-only.
• DRM_IVPU_PARAM_CAPABILITIES — the supported capabilities. read-only. the whole point of the vibe check 🔥
• DRM_IVPU_PARAM_PREEMPT_BUFFER_SIZE — the size of the preemption buffer. read-only.

the index field 🌈

index — the index for params that have multiple instances. so when a param isn't a one-off, this is how you say which one you mean. simple as that 🦋

the value field ⭐

value — the param value. the payload. the actual data. the whole reason we're here 💖

---

🎀 SEE ALSO 🎀

go read these next, bestie, they're all in the family:

• Kernel file ./include/uapi/drm/ivpu_accel.h
• contexts(9)
• DRM_IVPU_CAP_METRIC_STREAMER(9)
• DRM_IVPU_CAP_DMA_MEMORY_RANGE(9)
• DRM_IVPU_CAP_MANAGE_CMDQ(9)
• DRM_IVPU_CAP_BO_CREATE_FROM_USERPTR(9)
• struct drm_ivpu_bo_create(9)
• struct drm_ivpu_bo_create_from_userptr(9)
• struct drm_ivpu_bo_info(9)
• struct drm_ivpu_submit(9)
• struct drm_ivpu_cmdq_submit(9)
• struct drm_ivpu_bo_wait(9)
• struct drm_ivpu_metric_streamer_start(9)
• struct drm_ivpu_metric_streamer_get_data(9)
• struct drm_ivpu_cmdq_create(9)
• struct drm_ivpu_cmdq_destroy(9)
• struct drm_ivpu_metric_streamer_stop(9)

---

okay that's the whole page, you ate that 💅 this came out of ./include/uapi/drm, it's dated October 2026, and it's page struct drm_ivpu_param(9) of the Kernel API Manual — slay, go forth and read your parameters responsibly 🫶✨