adf_dev_started(9)

💖 adf_dev_started(9) — yeah that's the Kernel API Manual, bestie 💖

Okay so like… hi. Welcome to the adf_dev_started(9) page from the Kernel API Manual. Yes, the whole manual. We're doing this. Sit down, grab a lil snack 🍓, and let's get into it because this one is short and honestly kind of iconic for it.

---

✨ NAME ✨

adf_dev_started — the lil function that checks whether the device has actually started. That's it. That's the vibe check. 🦋

---

🌸 SYNOPSIS 🌸

int adf_dev_started (struct adf_accel_dev *accel_dev );

Like, that's the whole signature. Copy it exactly if you're writing it down, bestie, don't freestyle it 💅

---

🎀 ARGUMENTS 🎀

• accel_dev — a pointer to the acceleration device. That's the one you're checking up on. It's giving "hey girl are you up" energy, but for hardware 🫶

---

👑 DESCRIPTION 👑

So this one is to be used by QAT device specific drivers. That's the whole description. Fr fr. It's a helper for the QAT device specific drivers and nobody else, so don't go using it in random places and then acting surprised 😭

---

⭐ RETURN ⭐

• 1 — when the device has started ✅
• 0 — otherwise

That's the binary of it all. One or zero. Main character energy either way 👑

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/crypto/intel/qat/qat_common/adf_dev_mgr.c
• adf_clean_vf_map(9)
• adf_devmgr_update_class_index(9)
• adf_devmgr_add_dev(9)
• adf_devmgr_rm_dev(9)
• adf_devmgr_pci_to_accel_dev(9)
• adf_dev_in_use(9)
• adf_dev_get(9)
• adf_dev_put(9)
• adf_devmgr_in_reset(9)

Like the whole friend group honestly. Go read them too, they're all in the same lore 🙈

---

No warnings on this one! No dangerous flags, no deprecated anything. Just a cute lil check. Enjoy the calm before the next manpage 💀

---

And that's a wrap, bestie 🧚 Signing off with the source-y bits so nothing gets lost: the footer says ./drivers/crypto/intel/qat/qat... and the date is October 2026, and it's all still adf_dev_started(9) forever and ever. Slay 💜