ti_sci_cmd_rm_psil_unpair(9)

📦 version 7.3.1, in nixpkgs unstable

💅 ti_sci_cmd_rm_psil_unpair 💅

okay so picture this: you're deep in the Kernel API Manual (section 9, obvi), and you need to break up a PSI-L situationship. That's literally this function. It's the unpairing one — source thread, destination thread, we're separating them, no cap. 🦋

✨ NAME ✨

ti_sci_cmd_rm_psil_unpair — unpair a PSI-L source from a destination thread, bestie. that's the whole gig. 💖

🌸 SYNOPSIS 🌸

int ti_sci_cmd_rm_psil_unpair (const struct ti_sci_handle *handle , u32
nav_id , u32 src_thread , u32 dst_thread );

it's giving very int-returning, very four-arguments. she's not complicated, she's just specific. ✨

🎀 ARGUMENTS 🎀

  • handle — Pointer to TI SCI handle. this is your main character pointer, the one you gotta have. 👑
  • nav_id — Device ID of Navigator Subsystem which should be used for unpairing. yes, which should be used for unpairing — that's the vibe, that's the job. 🔥
  • src_thread — Source PSI-L thread ID. the one being unpaired from, iykyk. 💜
  • dst_thread — Destination PSI-L thread ID. the other half of the split. 💔

⭐ RETURN ⭐

returns 0 if all went well — slay, flawless, no notes 💅 — and otherwise it returns the appropriate error value. so like, check your return, bestie, always. 😭

🌈 SEE ALSO 🌈

Kernel file ./drivers/firmware/ti_sci.c. and then the whole extended friend group, fr fr — every single one of them, in order, no skips:

like, that's the whole group chat. every last one. 💀

ok real talk tho: src_thread and dst_thread are PSI-L thread IDs and nav_id is the Device ID of the Navigator Subsystem used for unpairing — so don't just vibe-check them, get them right. 🙈

<div align="center">🌸 🌸 🌸</div>

this lil page lives in ./drivers/firmware, dropped October 2026, and it's literally signed ti_sci_cmd_rm_psil_unpair(9). mwah. go unpair something, bestie. 💖✨🎀

📦 where this page comes from