ti_sci_cmd_...source_range(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 ti_sci_cmd_get_resource_range ✨

okay so this is a page straight out of the Kernel API Manual — you'll see it filed under ti_sci_cmd_...source_range(9) up in the header because the title got truncated mid-word (rude, honestly), but bestie the real name is ti_sci_cmd_get_resource_range and we're gonna get into it 💅

💖 NAME 💖

ti_sci_cmd_get_resource_range — grab a whole range of resources that are assigned to a host, where that host is the same as the ti sci interface host 🫶

🎀 SYNOPSIS 🎀

int ti_sci_cmd_get_resource_range (const struct ti_sci_handle *handle ,
u32 dev_id , u8 subtype , struct ti_sci_resource_desc *desc );

🌈 ARGUMENTS 🌈

okay so the args, one by one, no skipping 👑

  • handle — a pointer to the TISCI handle. that's your entry ticket, don't lose it 🎟️
  • dev_id — the TISCI device ID. literally which device we're talking about ✨
  • subtype — the resource assignment subtype that's being requested from the given device. yes, *sub*type, it's giving specificity 🌸
  • desc — pointer to a ti_sci_resource_desc that gets updated with the resource range start index and the number of resources. so it comes back changed, that's the whole point 💫

🔥 RETURN 🔥

0 if all went fine 😌 — otherwise it returns the appropriate error, so like, keep an eye on that return value fr fr 💀

🦋 SEE ALSO 🦋

so there's a lot of family here, buckle up bestie — the kernel file is ./drivers/firmware/ti_sci.c and these are all the siblings:

like I said — the whole extended family showed up to the group chat 😭🫶

ngl the vibe here is "I only need one range of resources and I need it now" — pass your handle, your dev_id, your subtype, and a desc to fill in, and you're iconic 💅

and that's the page bestie! 🎀 it lives over in ./drivers/firmware, dated October 2026, page name ti_sci_cmd_...source_range(9) — mwah, slay, periodt ✨💖

📦 where this page comes from