drm_mode_validate_driver(9)

📦 version 7.3.1, in nixpkgs unstable

💅 drm_mode_validate_driver(9)

okay bestie, so this is a page from the Kernel API Manual — like, the group chat of kernel documentation — and today's main character is drm_mode_validate_driver. she's a little validation girlie and honestly she ate ✨

🌸 NAME

drm_mode_validate_driver — make sure the mode is, like, somewhat sane 🫶

ngl "somewhat sane" is doing a lot of heavy lifting here but that's genuinely the vibe

🦋 SYNOPSIS

enum drm_mode_status drm_mode_validate_driver (struct drm_device *dev ,
const struct drm_display_mode *mode );

literally just hand her a device and a mode and she'll tell you what's up 💖

🎀 ARGUMENTS

  • dev — the drm device, aka the whole situation 👑
  • mode — the mode to check, the one on trial, the one getting a vibe check 🔍

🌈 DESCRIPTION

so the way this works is: first she does the basic validation on the mode — just the standard sanity stuff, no cap — and then she lets the driver have a turn. the driver gets to check for its own device/driver specific limitations through the optional drm_mode_config_helper_funcs.mode_valid hook 💅

the key word there is optional — iykyk, if the driver doesn't set that hook, that step just... doesn't happen. no drama, no error, she just moves on 🧚

⭐ RETURN

the mode status 💫 (that enum drm_mode_status from the synopsis, she gives it right back to you)

💜 SEE ALSO

kernel file: ./drivers/gpu/drm/drm_modes.c

and now the entire extended friend group, everyone say hi 👋:

okay that's the whole page, love u, go validate some modes responsibly 💜🦋

this one lives in ./drivers/gpu/drm and the version of record is dated October 2026 — so like, future girlie behavior fr fr 🎀✨💅

📦 where this page comes from