qcom_scm_generate_ice_key(9)

📦 version 7.3.1, in nixpkgs unstable

✨ qcom_scm_generate_ice_key ✨

okay so bestie, welcome to the qcom_scm_generate_ice_key(9) page — it's a kernel API manual entry and honestly it's giving "small function, big responsibilities" 💅

🌸 NAME 🌸

qcom_scm_generate_ice_key — literally generates a wrapped key for storage encryption 🔐

🦋 SYNOPSIS 🦋

int qcom_scm_generate_ice_key (u8 *lt_key , size_t lt_key_size );

🎀 ARGUMENTS 🎀

  • lt_key — the output buffer where the long-term wrapped key gets dropped off, bestie. That's where it lives now 💖
  • lt_key_size — the size of lt_key in bytes. And no, you can't just vibe-check this one: it must be the exact wrapped key size used by the SoC. Exact. Not "close enough." The SoC is not flexible about this, periodt ✨

💜 DESCRIPTION 💜

So the tea is: this bad boy generates a key using the built-in HW module in the SoC — like, the hardware does the actual work, main character energy 🔥

And the resulting key comes back wrapped with the platform-specific Key Encryption Key. Wrapped, bestie. That's the whole point 🎁

🫶 RETURN 🫶

  • 0 on success — slay 💅
  • -errno on failure — not slay 😭

🌈 SEE ALSO 🌈

Kernel file ./drivers/firmware/qcom/qcom_scm.c — go read it, iykyk 👑

ngl that's a lot of cross-references, but every single one of them is iconic in its own way 🧚‍♀️

k that's the whole page, mwah 💋 — this one came from ./drivers/firmware/qcom, dated October 2026, and it's the qcom_scm_generate_ice_key(9) manual, fr fr 🍓

📦 where this page comes from