intel_connector_debugfs_add(9)
π intel_connector_debugfs_add (9) β¨
okay so bestie, welcome to the Kernel API Manual β yes we're reading kernel docs together, this is our bonding time now π«Ά
πΈ NAME πΈ
intel_connector_debugfs_add β the girl whose whole job is adding i915 specific connector debugfs files π
β SYNOPSIS β
void intel_connector_debugfs_add (struct intel_connector *connector );
that's it. that's the whole vibe. a void function, no return value, no drama, no notes π
π¦ ARGUMENTS π¦
connectorβ pointer to a registeredintel_connector. like, it's gotta be registered already, that's the whole prerequisite, no cap β¨
π₯ DESCRIPTION π₯
so what happens after all these debugfs files get added? cleanup, babes. and not by you β the cleanup is done by drm_connector_unregister, which gets there through a call to drm_debugfs_connector_remove π
so yeah, you don't have to manually tidy up your little debugfs mess. the unregister path handles it for you. main character energy from drm_connector_unregister honestly π
π SEE ALSO π
- Kernel file
./drivers/gpu/drm/i915/display/intel_display_debugfs.cβ go read it iykyk π intel_crtc_debugfs_add(9)β the crtc sibling, equally iconic β
and that's the page!! mwah π this little doc lives in ./drivers/gpu/drm/i915/display, dated October 2026, and it's literally titled intel_connector_debugfs_add(9) β go forth and add those connector debugfs files bestie, the kernel believes in you π§π
π¦ 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