adf_dbgfs_add(9)

✨ adf_dbgfs_add(9) — Kernel API Manual ✨

okay bestie, welcome to the Kernel API Manual page for adf_dbgfs_add(9) — she's a function, she's in the kernel, and she's literally here to add some debugfs entries for you 🎀

---

🌸 NAME 🌸

adf_dbgfs_add — adds debugfs entries that are non-persistent, no cap 💅

---

🦋 SYNOPSIS 🦋

void adf_dbgfs_add (struct adf_accel_dev *accel_dev );

that's the whole signature, periodt ⭐

---

💖 ARGUMENTS 💖

• accel_dev — a pointer to the acceleration device. like, that's the one (1) thing you hand her, and she's off 🫶

---

👑 DESCRIPTION 👑

so what does she actually do? adf_dbgfs_add creates debugfs entries — and here's the key vibe check — these entries are not persistent through a device state change. as in, if the device goes from up to down, or from down to up, those entries don't survive the glow-up 😭🔁

basically: non-persistent debugfs entries, made fresh, iconically temporary 🌈

---

🔥 SEE ALSO 🔥

• Kernel file ./drivers/crypto/intel/qat/qat_common/adf_dbgfs.c
• adf_dbgfs_init(9)
• adf_dbgfs_exit(9)
• adf_dbgfs_rm(9)

go read those next bestie, they're all in the same friend group 💜

---

💀 reminder: the entries from adf_dbgfs_add are the non-persistent kind, so don't go expecting them to stick around after a device state change — that's the whole point, fr fr 🙈

---

and that's the page!! sign-off time 🧚: this one came from ./drivers/crypto/intel/qat/qat..., dated October 2026, and she's officially adf_dbgfs_add(9) forever and ever 🍓💖 slay!!