qcom_ice_prepare_key(9)

📦 version 7.3.1, in nixpkgs unstable

🧊 qcom_ice_prepare_key(9) — like, the Kernel API Manual one, bestie

okay so bestie, gather round, because we're about to talk about qcom_ice_prepare_key and honestly? it's giving crypto glow-up energy. ✨ this is the page from the Kernel API Manual and yes we're doing the whole thing, no skips, no cap. 💅

🎀 NAME 🎀

qcom_ice_prepare_key — prepare a wrapped key for inline encryption. that's it, that's the whole vibe. it takes a key that's already wrapped and wraps it again. iconic behaviour honestly 🦋

✨ SYNOPSIS ✨

int qcom_ice_prepare_key (struct qcom_ice *ice , const u8 *lt_key ,
       size_t lt_key_size , u8 eph_key[BLK_CRYPTO_MAX_HW_WRAPPED_KEY_SIZE] );

literally copy it exactly, don't @ me, this is the signature and she is not up for editing 🔥

💖 ARGUMENTS 💖

  • ice — the ICE driver data. ur main character struct, the whole context of the operation 🫶
  • lt_key — a long-term wrapped key. the original key, pre-glowing-up.
  • lt_key_size — size of lt_key, in bytes. we measure things around here 📏
  • eph_key — the output buffer for the ephemerally-wrapped key. yes it's u8 eph_key[BLK_CRYPTO_MAX_HW_WRAPPED_KEY_SIZE], yes that's the whole type, no we're not shortening it 💀

🌸 DESCRIPTION 🌸

so the actual tea: this one uses HWKM to re-wrap a long-term wrapped key with the per-boot ephemeral key.

that's the entire plot. key goes in long-term-wrapped, comes out ephemeral-wrapped. HWKM does the heavy lifting. no notes, she ate 👑

💅 RETURN 💅

  • on success? you get the size of the resulting wrapped key. slay 💖
  • if the long-term wrapped key you handed over is invalid? you get -EBADMSG. not the vibe. 😭
  • anything else? another -errno value, because the kernel loves a plot twist 🙈

🌈 SEE ALSO 🌈

the whole squad fr fr, go read them too 🧚

and that's the page, bestie! 🎀 brought to you by ./drivers/soc/qcom, dated October 2026 — yes, the future, we're ahead of schedule 💜 mwah, study ur ICE key wrapping, ily, bye! 🦋✨

📦 where this page comes from