drm_kunit_h...c_drm_device(9)

✨ NAME ✨

Okay bestie, this page is from the Kernel API Manual, and it's all about drm_kunit_helper_alloc_drm_device — it allocates a mock DRM device for KUnit tests 💅. Yes, this is that drm_kunit_h...c_drm_device(9) cutie. She's giving test-helper main character energy 🎀.

🦋 SYNOPSIS 🦋

drm_kunit_helper_alloc_drm_device (_test , _dev , _type , _member ,
       _feat );

🎀 ARGUMENTS 🎀

• _test — The test context object, aka the vibe holder for this test 🫶.
• _dev — The parent device object.
• _type — the type of the struct which contains struct drm_device.
• _member — the name of the drm_device within _type.
• _feat — Mocked DRM device driver features ✨.

🌸 DESCRIPTION 🌸

So this function creates a struct drm_driver, and then it will create a struct drm_device from _dev and that driver. Lowkey iconic setup behavior.

_dev should be allocated using drm_kunit_helper_alloc_device. No cap, that's the required move — not a suggestion, bestie 😭.

The driver is tied to the _test context and will get cleaned at the end of the test. The drm_device is allocated through devm_drm_dev_alloc and will thus be freed through a device-managed resource. So yeah, cleanup is handled, and that's honestly slay 🧚.

⭐ RETURN ⭐

A pointer to the new drm_device, or an ERR_PTR otherwise. That's it — either the cute new device pointer, or the error-pointer plot twist 💀.

👑 SEE ALSO 👑

• Kernel file ./include/drm/drm_kunit_helpers.h
• drm_kunit_helper_alloc_drm_device_with_driver(9)

Okay that's the whole page, bestie 💖 — this one comes from ./include/drm, dated October 2026, and the page title is drm_kunit_h...c_drm_device(9). Go forth and test your DRM device allocation with main character confidence 🌈👑.