STRUCT TI_SCI_MSG_RESP_GET_RESOURCE_RANGE(9)

💖 struct ti_sci_msg_resp_get_resource_range — from the Kernel API Manual, bestie ✨

Okay so picture this: you're deep in the kernel docs, the section is literally called struct ti_s...source_range(9), and you're like "what even is this." Don't worry, I got you. It's the response to resource get range — like, the reply you get back. Let's go 🫶

---

✨ SYNOPSIS ✨

The whole struct, served fresh, no notes:

struct ti_sci_msg_resp_get_resource_range {
    struct ti_sci_msg_hdr hdr;
    u16 range_start;
    u16 range_num;
    u16 range_start_sec;
    u16 range_num_sec;
 };

That's it, that's the vibe. Four little u16 friends and a header. Slay 💅

---

🌸 Members 🌸

Every field, bestie, and what it's giving:

• hdr — the generic header. Every message in this family rocks one, it's the main character of headers 👑
• range_start — the start index of the first resource range. Where range number one begins ✨
• range_num — how many resources live in that first range. The headcount 🔢
• range_start_sec — the start index of the second resource range. Yeah, there's a second one, she's lowkey underrated 💜
• range_num_sec — number of resources in that second range. Second range, second headcount, equally important fr fr 🌈

---

🦋 Description 🦋

It's a response to request — specifically the reply to TI_SCI_MSG_GET_RESOURCE_RANGE. So when something asks "hey, what's the resource range situation," this struct is what comes back. Periodt. 🎀

---

👑 SEE ALSO 👑

Everything you should also read, in all its glory — the kernel file lives at ./drivers/firmware/ti_sci.h, and these are the struct siblings:

• struct ti_sci_msg_hdr(9)
• struct ti_sci_msg_resp_version(9)
• struct ti_sci_msg_req_reboot(9)
• struct ti_sci_msg_resp_query_fw_caps(9)
• struct ti_sci_msg_req_set_device_state(9)
• struct ti_sci_msg_req_get_device_state(9)
• struct ti_sci_msg_resp_get_device_state(9)
• struct ti_sci_msg_req_set_device_resets(9)
• struct ti_sci_msg_req_set_clock_state(9)
• struct ti_sci_msg_req_get_clock_state(9)
• struct ti_sci_msg_resp_get_clock_state(9)
• struct ti_sci_msg_req_set_clock_parent(9)
• struct ti_sci_msg_req_get_clock_parent(9)
• struct ti_sci_msg_resp_get_clock_parent(9)
• struct ti_sci_msg_req_get_clock_num_parents(9)
• struct ti_sci_msg_resp_get_clock_num_parents(9)
• struct ti_sci_msg_req_query_clock_freq(9)
• struct ti_sci_msg_resp_query_clock_freq(9)
• struct ti_sci_msg_req_set_clock_freq(9)
• struct ti_sci_msg_req_get_clock_freq(9)
• struct ti_sci_msg_resp_get_clock_freq(9)
• struct ti_sci_msg_req_prepare_sleep(9)
• struct ti_sci_msg_req_set_io_isolation(9)
• struct ti_sci_msg_resp_lpm_wake_reason(9)
• struct ti_sci_msg_req_lpm_set_device_constraint(9)
• struct ti_sci_msg_req_lpm_set_latency_constraint(9)
• struct ti_sci_msg_req_get_resource_range(9)
• struct ti_sci_msg_req_manage_irq(9)
• struct ti_sci_msg_rm_ring_cfg_req(9)
• struct ti_sci_msg_psil_pair(9)
• struct ti_sci_msg_psil_unpair(9)
• struct ti_sci_msg_udmap_rx_flow_cfg(9)
• struct rm_ti_sci_msg_udmap_rx_flow_opt_cfg(9)
• struct ti_sci_msg_rm_udmap_tx_ch_cfg_req(9)
• struct ti_sci_msg_rm_udmap_rx_ch_cfg_req(9)
• struct ti_sci_msg_rm_udmap_flow_cfg_req(9)
• struct ti_sci_msg_req_proc_request(9)
• struct ti_sci_msg_req_proc_release(9)
• struct ti_sci_msg_req_proc_handover(9)
• struct ti_sci_msg_req_set_config(9)
• struct ti_sci_msg_req_set_ctrl(9)
• struct ti_sci_msg_req_get_status(9)
• struct ti_sci_msg_resp_get_status(9)

Like, that's a whole friend group and this struct is definitely in it 💀💖

---

Ngl this page lives under ./drivers/firmware — that's home base 🏠

And that's the whole thing! Written October 2026, straight from the ./drivers/firmware docs — go read the source, bestie, iykyk 🌟🧚‍♀️