STRUCT TI_SCI_MSG_REQ_GET_RESOURCE_RANGE(9)

🦋 struct ti_sci_msg_req_get_resource_range(9) 🦋

okay so bestie, we're in the Kernel API Manual today and this one's literally the ✨ask-nicely✨ struct for "hey firmware, what resources did you give my host?" No cap, it's giving polite request energy. 🎀

---

🌸 NAME 🌸

struct ti_sci_msg_req_get_resource_range — the request that goes "hi, what's the range of resources assigned to this host?" 💖

---

✨ SYNOPSIS ✨

struct ti_sci_msg_req_get_resource_range {
    struct ti_sci_msg_hdr hdr;
  #define MSG_RM_RESOURCE_TYPE_MASK       GENMASK(9, 0);
  #define MSG_RM_RESOURCE_SUBTYPE_MASK    GENMASK(5, 0);
    u16 type;
    u8 subtype;
    u8 secondary_host;
 };

---

🫶 Members 🫶

• hdr — the generic header, the little main-character intro every message gets 💅
• type — the unique resource assignment type (this is the big vibe check on what kind of resource we're talking about)
• subtype — the resource assignment subtype within the resource type, iykyk 🌈
• secondary_host — the host processing entity that the resources get allocated to 🧚 This one's only needed when the destination host id is different from the ti sci interface host id — otherwise you can just pass TI_SCI_IRQ_SECONDARY_HOST_INVALID and keep it moving 🙈

---

💜 Description 💜

The request type is TI_SCI_MSG_GET_RESOURCE_RANGE 🔥 It comes back answered with the requested resource range, which is of type TI_SCI_MSG_GET_RESOURCE_RANGE — so like, the response matches, periodt ✨

---

👑 SEE ALSO 👑

Kernel file ./drivers/firmware/ti_sci.h — and bestie, the whole friend group shows up here, so buckle in 🎀

• 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_resp_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)

---

and that's the whole page, bestie, we ate 💅💖 this little gem lives over in ./drivers/firmware, stamped October 2026, and the header's still rocking its dramatically abbreviated self: struct ti_sc...source_range(9) 😭🫶 go forth and request your ranges, queen 👑