adf_fw_counters_dbgfs_add(9)

💅 adf_fw_counters_dbgfs_add — like, the Kernel API Manual page, bestie ✨

okay so welcome to the adf_fw_counters_dbgfs_add(9) glow-up, straight out of the Kernel API Manual 🎀 this one's a little void function that makes debugfs do something cute. let's get into it 🫶

---

✨ NAME ✨

adf_fw_counters_dbgfs_add — creates a debugfs file that's literally holding your FW execution counters 💖

---

🌸 SYNOPSIS 🌸

void adf_fw_counters_dbgfs_add (struct adf_accel_dev *accel_dev );

that's it. that's the whole vibe check. returns nothing, takes one pointer 👑

---

🦋 ARGUMENTS 🦋

• accel_dev — a pointer to a QAT acceleration device. that's your main character right there, no cap.

---

💜 DESCRIPTION 💜

so the way this function works is honestly iconic: it creates a file 📁 so you can display a table — a whole little statistics moment — for the given QAT acceleration device.

and what's in this table? device-specific execution values for each AE 🧚 like bestie, it's storing:

• the number of requests sent to the FW 🔥
• and the responses received from the FW 💌

that's the whole thing. simple, effective, ate. 💅

---

⭐ RETURN ⭐

void — literally nothing comes back. she gives, she doesn't take 🙈

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/crypto/intel/qat/qat_common/adf_fw_counters.c
• adf_fw_counters_get(9)
• adf_fw_counters_dbgfs_rm(9)

those last two are the siblings fr fr — one goes and gets the counters, the other cleans up the debugfs file 🎀 iykyk

---

💀 reminder bestie: this is the add half of the duo. adf_fw_counters_dbgfs_rm(9) is the one that takes the file back out. don't leave her hanging.

---

mwah 💋 that's the page! brought to you by the Kernel API Manual, sourced from ./drivers/crypto/intel/qat/qat..., dated October 2026 ⭐ and yes she's still signing off as adf_fw_counters_dbgfs_add(9) because consistency is a slay 💖🧚‍♀️🦋