drm_kunit_he...tc_connector(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ drm_kunit_he...tc_connector ✨

okay so bestie, this one lives in the Kernel API Manual (yes, the whole kernel, it's a lot, we love that for it) πŸ’…


🌸 NAME 🌸

drm_kunit_helper_enable_crtc_connector β€” literally just enables a CRTC -> Connector output. that's the whole vibe ✨


πŸŽ€ SYNOPSIS πŸŽ€

int drm_kunit_helper_enable_crtc_connector (struct kunit *test , struct
drm_device *drm , struct drm_crtc *crtc , struct drm_connector
*connector , const struct drm_display_mode *mode , struct
drm_modeset_acquire_ctx *ctx );

like yeah, six arguments, she's high-maintenance but she delivers 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • test β€” the test context object, aka the main character of this whole operation πŸ‘‘
  • drm β€” the device to alloc the plane for, no big deal, just the entire DRM device 😭
  • crtc β€” the CRTC you're enabling πŸ’–
  • connector β€” the Connector you're enabling, they come as a pair, iykyk πŸ”₯
  • mode β€” the display mode to configure the CRTC with ⭐
  • ctx β€” locking context, pls respect her πŸ™ˆ

πŸ’œ DESCRIPTION πŸ’œ

so the way this works: drm_kunit_helper_enable_crtc_connector creates an atomic update that enables the route from crtc to connector, with the given mode. like it's literally building the whole path, no cap 🧚

⚠️ and here's the part where you gotta pay attention bestie: you get a pointer to the new CRTC, or an ERR_PTR otherwise. and if the error returned is EDEADLK, the entire atomic sequence must be restarted. like fully restart it. no shortcuts, fr fr πŸ’€

🌈 SEE ALSO 🌈

all her friends, go say hi, they ate πŸ“


and that's the page!! sign-off time: this lil beauty comes from ./drivers/gpu/drm/tests, dated October 2026, and the page is drm_kunit_he...tc_connector(9) just in case you forgot where you were πŸ’– slay, go write some kunit tests, ily πŸŽ€

<!--chunk:9-->

πŸ“¦ where this page comes from