qcomtee_object_id_get(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… qcomtee_object_id_get(9) πŸ’…

okay bestie, welcome to the Kernel API Manual page for qcomtee_object_id_get(9). we are literally getting an ID for an object so it can be sent to QTEE, and we're gonna be accurate about it. 🫢


🌸 NAME 🌸

qcomtee_object_id_get β€” get an ID for an object to send to QTEE. that's the assignment. iconic. ✨

πŸ¦‹ SYNOPSIS πŸ¦‹

       int qcomtee_object_id_get (struct qcomtee_object_invoke_ctx *oic ,
       struct qcomtee_object *object , unsigned int *object_id );

πŸŽ€ ARGUMENTS πŸŽ€

  • oic β€” context to use for the invocation. like, the situation you're operating in, bestie. πŸ’–
  • object β€” object to assign an ID. yes, that object. give it the ID. slay.
  • object_id β€” object ID. that's the ID. periodt.

πŸ’– DESCRIPTION πŸ’–

Called on the path to QTEE to construct the message; see qcomtee_prepare_msg and qcomtee_update_msg.

real talk: this is the one that shows up on the path to QTEE while the message is being constructed. if you want the surrounding lore, those two functions above are your besties. no extra mystery, no invented side quests β€” that's the description. 🧚

πŸ”₯ RETURN πŸ”₯

  • On success, returns 0. clean, correct, a little slay. βœ…
  • On failure, returns < 0. not the vibe, but now you know. πŸ’€

🌈 SEE ALSO 🌈

the kernel file is ./drivers/tee/qcomtee/core.c, and here's the whole friend group:


mwah πŸ’‹ this page came from the ./drivers/tee/qcomtee source/version, dated October 2026, and it's the qcomtee_object_id_get(9) manual page. byeee 🫢

πŸ“¦ where this page comes from