ti_sci_cmd_dev_is_valid(9)

📦 version 7.3.1, in nixpkgs unstable

💅 ti_sci_cmd_dev_is_valid(9) — like, the Kernel API Manual page, bestie 🎀

okay so real talk, this page is from the Kernel API Manual and it's about one (1) tiny little function that just checks if a device ID is even valid. baby function. iconic behaviour. let's get into it ✨

🌸 NAME 🌸

ti_sci_cmd_dev_is_valid — literally asking "is this device valid or not" 💖

🦋 SYNOPSIS 🦋

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

so it takes your handle, takes your id, and gives you back an int. that's the whole vibe. no cap.

✨ ARGUMENTS ✨

  • handle — a pointer to the TISCI handle, the one you got from *ti_sci_get_handle. yes bestie you have to actually get the handle first, can't just manifest it 🙈
  • id — the Device Identifier. like, the ID of the device. the device's whole identity fr fr.

👑 RETURN 👑

returns 0 if everything went fine and the device ID is valid 🫶 otherwise it returns the appropriate error — so like, if it's not valid, you get an error code and you deal with it, periodt. 💀

🌈 SEE ALSO 🌈

okay this is the part where the manpage just casually drops the entire friend group 💅 the kernel file is ./drivers/firmware/ti_sci.c and honestly the whole squad is here:

like I said. the whole friend group. iykyk 🧚

lowkey the entire page is just "is the device valid, yes or no" and honestly? relatable. sometimes you just need a yes or no from the universe. ⭐

and that's the whole thing bestie — this one lives over in ./drivers/firmware and it's dated October 2026, so it's giving future-forward main character energy 👑💜 mwah, go check your device IDs, ily 🍓

📦 where this page comes from