qcom_tzmem_pool_new(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ qcom_tzmem_pool_new ✨

okay so bestie, we're in the Kernel API Manual today and this one is a kernel function β€” a real one, from the Qualcomm TrustZone memory corner of the tree 🫢 stay with me, it's actually so good.

πŸ’– NAME πŸ’–

qcom_tzmem_pool_new β€” literally just creates a new TZ memory pool. that's it, that's the whole job, and it does it iconically πŸ’…

🌸 SYNOPSIS 🌸

struct qcom_tzmem_pool * qcom_tzmem_pool_new (const struct qcom_tzmem_pool_config *config );

so you hand it a config and it gives you back a struct qcom_tzmem_pool *. yes queen, pointer to a pool ✨

πŸŽ€ ARGUMENTS πŸŽ€

  • config β€” the pool configuration. it's a const struct qcom_tzmem_pool_config *, aka the vibe spec for your new pool. tell it what you want and it'll build it πŸ¦‹

🧚 DESCRIPTION 🧚

okay so what this does: it creates a new pool of memory suitable for sharing with the TrustZone. that's the whole tea β˜• β€” you're making a memory pool that's allowed to hang out with TrustZone, which is a whole separate secure world, so like... it's giving main character energy but with security implications, iykyk.

⚠️ big warning bestie, no cap: it must not be used in atomic context. like, do not. that's a hard no. don't try it, don't be cute about it, don't "just this once" it. πŸ™ˆ

πŸ”₯ RETURN πŸ”₯

you get back either:

  • the new memory pool address πŸ’– (slay, it worked)
  • or ERR_PTR on error 😭 (check it, always check it, IS_ERR() is your bestie)

🌈 SEE ALSO 🌈


okay that's the whole page, you ate that πŸ’… this one lives under ./drivers/firmware/qcom, it's from October 2026, and it's part of the Kernel API Manual (the version-y footer situation). go forth and pool responsibly, bestie πŸ“βœ¨

πŸ“¦ where this page comes from