dpu_rm_get_...ed_resources(9)

📦 version 7.3.1, in nixpkgs unstable

💅 dpu_rm_get_assigned_resources(9)

okay so this is a page straight out of the Kernel API Manual, and honestly? it's a little guy with a very long name. like, the title itself is dpu_rm_get_...ed_resources(9) because apparently even the docs got tired of typing it out 😭. bestie, we're talking about the DPU resource manager, and this function is the one that tells you what hardware you actually got handed. let's get into it 💖

✨ NAME ✨

dpu_rm_get_assigned_resources — get hw resources of the given type that are assigned to this encoder 🎀

like literally, you ask "hey what hardware of this type got assigned to this encoder" and it tells you. no cap.

🌸 SYNOPSIS 🌸

int dpu_rm_get_assigned_resources (struct dpu_rm *rm , struct
dpu_global_state *global_state , struct drm_crtc *crtc , enum
dpu_hw_blk_type type , struct dpu_hw_blk **blks , int blks_size );

it's giving six arguments and an int return, and yes you need all of them 🙈

🦋 ARGUMENTS 🦋

  • rm — the DPU Resource Manager handle. your main character struct, the one holding all the resource bookkeeping 💅
  • global_state — resources shared across multiple kms objects. the communal vibe check, iykyk 🫶
  • crtc — the DRM CRTC handle. this is the encoder-ish thing we're asking about ✨
  • type — the resource type to return data for. like, which flavor of hw blk do you want, bestie 🍓
  • blks — pointer to the array to be filled by HW resources. you bring the bucket, it fills the bucket 🪣
  • blks_size — the size of the blks array. please tell it how big your bucket is, fr fr 🙏

👑 SEE ALSO 👑

kernel file ./drivers/gpu/drm/msm/disp/dpu1/dpu_rm.c and friends:

go read them, they're all part of the same little friend group 💜

and that's the whole page, bestie — no more sections hiding in the back. this one's from the Kernel API Manual, lives under ./drivers/gpu/drm/msm/disp/dpu1, and the date stamp on it is October 2026. dpu_rm_get_...ed_resources(9) out 🌈💖✨

📦 where this page comes from