devm_qcom_tzmem_pool_new(9)

📦 version 7.3.1, in nixpkgs unstable

💅 devm_qcom_tzmem_pool_new(9) — like, the managed era of TZ memory pools ✨

okay bestie, welcome to the Kernel API Manual 🎀 this one's short but she's important. and yes, the title is literally devm_qcom_tzmem_pool_new(9), we're not being subtle today 💖

🌸 NAME 🌸

devm_qcom_tzmem_pool_new — it's the managed variant of qcom_tzmem_pool_new(). that's it, that's the vibe. devm does the cleanup so you don't have to 🫶

✨ SYNOPSIS ✨

struct qcom_tzmem_pool * devm_qcom_tzmem_pool_new (struct device *dev ,
const struct qcom_tzmem_pool_config *config );

like look at her. two args, one return, zero drama 💅

🦋 ARGUMENTS 🦋

  • dev — the struct device * that's managing this resource. bestie's on cleanup duty, that's literally the whole point of devm 🧚
  • config — the const struct qcom_tzmem_pool_config * pool configuration. all your settings go here, no cap ✨

💜 DESCRIPTION 💜

⚠️ real talk: must not be used in atomic context. that's the entire description. do not try it. do not pass go. it's giving "sleepy function" energy and atomic context is not the place for that 🙈

bestie please. not in atomic context. i'm begging 🫶

👑 RETURN 👑

you get back the address of the managed pool ✨ …or an ERR_PTR on failure 😭 so like, check it. always check it. IS_ERR() is your friend fr fr 💀

🌈 SEE ALSO 🌈

the kernel file that lives here, in all her glory:

./drivers/firmware/qcom/qcom_tzmem.c

and the whole friend group:

they all ate, honestly 💅

and that's the page, bestie 🎀 sourced from ./drivers/firmware/qcom, dated October 2026, closing out as devm_qcom_tzmem_pool_new(9) like the icon she is ⭐ go forth and manage your memory pools responsibly 💖

📦 where this page comes from