mei_hdcp_ver...t_prepare_km(9)

📦 version 7.3.1, in nixpkgs unstable

✨ NAME ✨

okay bestie, so this is the Kernel API Manual page for mei_hdcp_verify_receiver_cert_prepare_km (the header up top truncates it all cute as mei_hdcp_ver...t_prepare_km(9) 💅) — and what it does is literally Verify the Receiver Certificate AKE_Send_Cert and prepare AKE_Stored_Km/AKE_No_Stored_Km. no cap, that's the whole vibe 🎀

🌸 SYNOPSIS 🌸

int mei_hdcp_verify_receiver_cert_prepare_km (struct device *dev ,
struct hdcp_port_data *data , struct hdcp2_ake_send_cert *rx_cert , bool
*km_stored , struct hdcp2_ake_no_stored_km *ek_pub_km , size_t *msg_sz
);

like, she takes six arguments and returns an int, periodt 💖

🦋 ARGUMENTS 🦋

okay so here's the whole cast, main character energy each one:

  • dev — the device corresponding to the mei_cl_device 🫶
  • data — Intel HW specific hdcp data (iykyk, vendor-specific vibes)
  • rx_cert — the AKE_Send_Cert that's getting verified, put her under the microscope 🔍
  • km_stored — the pairing status flag output, she's an output bestie, not an input
  • ek_pub_km — the AKE_Stored_Km/AKE_No_Stored_Km output msg 📨
  • msg_sz — size of the AKE_XXXXX_Km output msg, gotta know how big the whole thing is ngl

⭐ RETURN ⭐

  • 0 on Success 🎉
  • <0 on Failure 💀

that's it, that's the whole scoring system, very "pass/fail class" of her honestly

🌈 SEE ALSO 🌈

go look at these, they're all in the same friend group fr fr:

lowkey a serve that this whole page lives out of ./drivers/misc/mei/hdcp 🐚

and that's a wrap bestie, mwah 💋 — this iconic little page is dated October 2026, straight from the kernel docs source of ./drivers/misc/mei/hdcp, titled mei_hdcp_ver...t_prepare_km(9) in the Kernel API Manual. slay, bye! 💜

📦 where this page comes from