STRUCT DRM_DEBUGFS_INFO(9)

💅 struct drm_debugfs_info(9) — from the Kernel API Manual, bestie

okay so picture this: it's struct drm_debugfs_info(9), straight out of the Kernel API Manual, and she is the debugfs info list entry. yes, that's her whole job. iconic behavior honestly 🎀

---

✨ NAME ✨

struct drm_debugfs_info — the debugfs info list entry, no cap 💖

---

🌸 SYNOPSIS 🌸

struct drm_debugfs_info {
    const char *name;
    int (*show)(struct seq_file*, void*);
    u32 driver_features;
    void *data;
 };

look at her. four members. flawless. 🦋

---

👑 Members 👑

• name — literally just the file name. that's it. that's the whole vibe 💅
• show — the show callback 🎬 and here's the tea: seq_file->private gets set to the struct drm_debugfs_entry that corresponds to the instance of this info on a given struct drm_device. so like, one info → many entries, one per device instance. iykyk ✨
• driver_features — the required driver features for this entry. gatekeeping, but make it legitimate 🚧
• data — driver-private data, and bestie listen: it should not be device-specific. keep it generic or catch these hands 🙈

---

🧚 Description 🧚

this structure represents a debugfs file that the drm core is gonna create for you. that's the whole arc. main character energy from a struct that just holds four fields 🌈

---

💜 SEE ALSO 💜

• Kernel file ./include/drm/drm_debugfs.h 📁
• DRM_DEBUGFS_GPUVA_INFO(9)
• struct drm_info_list(9)
• struct drm_info_node(9)
• struct drm_debugfs_entry(9)

go read them. all of them. obsessed 🫶

---

🍓 reminder bestie: data is not device-specific. i said what i said.

---

and that's the page!! sourced from the ./include/drm gang, dated October 2026, filed under struct drm_debugfs_info(9) — slay, go create some debugfs files, you got this ⭐💖