drm_connecto...ible_encoder(9)

📦 version 7.3.1, in nixpkgs unstable

💅 drm_connecto...ible_encoder(9) — a Kernel API Manual moment

okay so bestie, welcome to the Kernel API Manual ✨ this one's a lil function called drm_connector_has_possible_encoder, and honestly? it's giving "are these two even associated" energy. let's get into it 🫶

✨ NAME ✨

drm_connector_has_possible_encoder — check if the connector and encoder are associated with each other 💖

like, are they besties or not. that's the whole vibe check.

🌸 SYNOPSIS 🌸

bool drm_connector_has_possible_encoder (struct drm_connector *connector
, struct drm_encoder *encoder );

literally just hand it a connector and an encoder and it tells you if they're linked 💫 (and yes, it returns a bool, we love a clean yes/no)

🎀 ARGUMENTS 🎀

  • connector — the connector 👑 she's the one we're checking on
  • encoder — the encoder 🌈 the one we're checking against, iykyk

⭐ RETURN ⭐

<cute>True</cute> if encoder is one of the possible encoders for connector 💀✨

that's it. that's the answer. no cap.

🦋 SEE ALSO 🦋

okay so this list is long — like, unreasonably long — but every single one of these is iconic in her own right, so here we go, no skipping, periodt:

bestie i counted and yes, standard connector properties(9) really does show up twice — that's not me being chaotic, that's just how the page is 💀 keep both, she's earning her spot.

and that's the page!! 🧚‍♀️ straight outta the ./drivers/gpu/drm source, dated October 2026 — mwah, slay, go check your encoders 💅🎀💜

📦 where this page comes from