drm_dev_get(9)
π drm_dev_get(9) β the Kernel API Manual glow-up π
okay so bestie, welcome to the drm_dev_get page β it's from the Linux Kernel API Manual and it's literally about taking a reference on a DRM device π
β¨ NAME β¨
drm_dev_get β take a reference of a DRM device π«Ά
πΈ SYNOPSIS πΈ
void drm_dev_get (struct drm_device *dev );
π¦ ARGUMENTS π¦
devβ the device you wanna take a reference of... orNULL, bestie, no judgment π
β DESCRIPTION β
So what this does is it bumps the ref-count of dev up by one. That's it. That's the whole vibe. β¨
β οΈ but like, fr fr β you must already own a reference when you call this. not optional. no cap.
When you're done with it, use drm_dev_put to drop this reference again, okay? π«Ά
This function never fails. iconic behavior honestly π. However β and this is the important part, so listen up β this function does not provide any guarantee whether the device is alive or running π. It only provides a reference to the object and the memory associated with it. that's it. that's all it's giving π
π₯ SEE ALSO π₯
- Kernel file
./drivers/gpu/drm/drm_drv.c driver instance overview(9)drm_put_dev(9)drm_dev_enter(9)drm_dev_exit(9)drm_dev_unplug(9)drm_dev_set_dma_dev(9)drm_dev_wedged_event(9)component helper usage recommendations(9)__drm_dev_alloc(9)drm_dev_alloc(9)drm_dev_put(9)drmm_cgroup_register_region(9)drm_dev_register(9)drm_dev_unregister(9)
π that's the whole page, bestie!! this one lives in ./drivers/gpu/drm, dated October 2026, and it's page drm_dev_get(9) of the Kernel API Manual. go forth and handle your ref-counts responsibly π§π
π¦ 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