ti_sci_cmd_i...ce_exclusive(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

ti_sci_cmd_idle_device_exclusive β€” the command that idles a device managed by TISCI that is exclusively owned by the host doing the asking πŸŽ€ (yes, owned-owned, like it's got your name on it)

okay bestie, quick vibe check first: this page lives in the Kernel API Manual, and honestly, it's giving "small function, big responsibility" energy. let's get into it πŸ¦‹


✨ SYNOPSIS ✨

int ti_sci_cmd_idle_device_exclusive (const struct ti_sci_handle *handle
, u32 id );

like, that's the whole call. two arguments. no surprises. slay πŸ’…


🌸 ARGUMENTS 🌸

  • handle β€” pointer to the TISCI handle, as retrieved by *ti_sci_get_handle. it's your little all-access pass to the firmware, you literally cannot do this without it 🫢
  • id β€” the Device Identifier. which device? this number. that's it. that's the whole vibe.

πŸ”₯ DESCRIPTION πŸ”₯

so the call is a request for the device β€” and here comes the part where you actually read the note, bestie, because it's in ALL CAPS for a reason 😭

NOTE: the client MUST maintain integrity of the usage count by balancing get_device with put_device. No refcounting is managed by the driver for that purpose.

translating from manpage-ese: the driver is not gonna hold your hand and babysit a reference count for you. you get, you put. you balance them. if you don't, that's on you, and the universe will know πŸ’€ no cap.


🌈 RETURN 🌈

  • 0 β€” if all went fine ✨ (the good ending)
  • else β€” it returns the appropriate error 😭 (so like, check it, don't just assume)

πŸ¦‹ SEE ALSO πŸ¦‹

the friend group πŸ’œ β€” first up, the kernel file this all hangs out in: ./drivers/firmware/ti_sci.c

then the whole crew:


and that's the whole page, bestie β€” no crumbs left behind πŸ“

tiny sign-off: this lil legend comes from ./drivers/firmware, dated October 2026, and it answers to the name ti_sci_cmd_i...ce_exclusive(9). iconic, honestly πŸ‘‘βœ¨
πŸ“¦ where this page comes from