qcomtee_remove(9)

💅 qcomtee_remove(9) — Kernel API Manual 💅

okay bestie, welcome to the tiny but iconic corner of the Kernel API Manual about qcomtee_remove(9) ✨ this one is short, sweet, and very "cleanup era" 💖

🌸 NAME 🌸

qcomtee_remove — Device Removal Routine. 🧹✨

🦋 SYNOPSIS 🦋

void qcomtee_remove (struct platform_device *pdev );

🎀 ARGUMENTS 🎀

• pdev — platform device information struct. literally the platform device info struct, bestie 🫶

🔥 DESCRIPTION 🔥

So the platform subsystem calls this to alert the driver that it should release the device — like the kernel tapping the driver on the shoulder and being all "hey, time to let go, bestie" 💅

QTEE does not provide an API to inform it about a callback object going away. that's just the situation, no cap 😭

But here's the slay part: when releasing QTEE objects, any callback object sent to QTEE previously would be released by QTEE as part of the object release. so the cleanup is lowkey handled as part of that object release flow 🧚✨

👑 SEE ALSO 👑

Kernel file ./drivers/tee/qcomtee/call.c — yes, that's the spot 📂

• qcomtee_context_add_qtee_object(9)
• qcomtee_context_del_qtee_object(9)
• qcomtee_objref_to_arg(9)
• qcomtee_objref_from_arg(9)
• qcomtee_params_to_args(9)
• qcomtee_params_from_args(9)
• qcomtee_object_invoke(9)
• qcomtee_supp_recv(9)
• qcomtee_supp_send(9)
• qcomtee_get_qtee_feature_list(9)

mwah 💋 signing off from the source spot ./drivers/tee/qcomtee — dated October 2026 — and yes bestie, this page is still qcomtee_remove(9) 🌈💖