ti_sci_cmd_put_device(9)

📦 version 7.3.1, in nixpkgs unstable

💅 ti_sci_cmd_put_device(9) — the Kernel API Manual moment

okay so bestie, welcome to the glow-up era of the TISCI device lifecycle ✨ this one is a Kernel API Manual page (yes, the actual manual, we're fancy now), and it's all about giving a device back when you're done with it. no cap, it's short but it MATTERS. 🎀

🌸 NAME 🌸

ti_sci_cmd_put_device — the command that releases a device managed by TISCI 🫶

✨ SYNOPSIS ✨

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

like, that's the whole signature. short king. 👑

🎀 ARGUMENTS 🎀

  • handle — pointer to the TISCI handle, the one you got back from *ti_sci_get_handle 💖
  • id — the Device Identifier. which device, bestie. you gotta say which one. 🔍

🦋 DESCRIPTION 🦋

so this is the request for the device — i.e. the release side of the whole thing. and here's the part where you gotta pay attention because it's literally in all caps in the original for a reason:

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

translation, bestie: you are the refcount. the driver is not keeping score for you. every get_device needs its matching put_device or the count drifts and it's giving chaos. balance your books. periodt. 🧾✨

🔥 RETURN 🔥

0 if all went fine — iconic, we love a zero 🎉 — else it returns the appropriate error. so like, check it. don't just vibe past it. 😭

👑 SEE ALSO 👑

the whole friend group, in order, no one left out 🫶:

Kernel file ./drivers/firmware/ti_sci.c

that's the whole page, bestie, you ate that 💅 this little gem lives in ./drivers/firmware, dated October 2026, and yeah — the page itself is ti_sci_cmd_put_device(9). now go balance your refcounts, ily, bye 🫶💖🌸

📦 where this page comes from