hisi_qm_get_dfx_access(9)

📦 version 7.3.1, in nixpkgs unstable

💅 hisi_qm_get_dfx_access — a kernel API manual moment

okay so bestie, you're looking at the hisi_qm_get_dfx_access(9) page, and yes it's from the Kernel API Manual — v fancy, v kernel, we love that for us 🎀

✨ NAME ✨

hisi_qm_get_dfx_access — the "lemme try to get dfx access" girlie 💅 literally what it says on the tin.

🌸 SYNOPSIS 🌸

int hisi_qm_get_dfx_access (struct hisi_qm *qm );

that's it. that's the whole signature. she's short, she's sweet, she takes one (1) argument 🦋

🫶 ARGUMENTS 🫶

  • qm — pointer to the accelerator device. like, the actual device object. no cap, that's your whole input ✨

🔥 DESCRIPTION 🔥

so here's the vibe: you call this to try to get dfx access, and then the user can get message. that's the whole point of her existence, periodt 💖

and there's a little conditional situation going on — read carefully bestie:

  • if the device is in suspended, it returns failure. no access for you, sorry babe 😭
  • otherwise, it bumps up the runtime PM usage counter — like a little "hey, I'm using this rn" tap on the shoulder 👑
lowkey important: the suspend check is the vibe check here. suspended device = failure, full stop. don't come for her, she told you 💀

🌈 SEE ALSO 🌈

okay this list is long and honestly iconic — like she knows everybody in the building. all of these live in the kernel file ./drivers/crypto/hisilicon/qm.c:

like??? she's connected. iykyk 🧚

aaaand that's the page!! short, sweet, extremely specific, we stan 💜 this little beauty comes to you from ./drivers/crypto/hisilicon, dated October 2026 — go off, kernel docs, you ate 🔥👑

📦 where this page comes from