devm_ti_sci_get_resource(9)

💅 devm_ti_sci_get_resource(9) 💅

okay so this is a page from the Kernel API Manual, and it's here to explain devm_ti_sci_get_resource — the resource-range getter bestie. No cap, it's literally about getting a resource range assigned to the device. ✨

---

📛 NAME 📛

devm_ti_sci_get_resource — get a resource range assigned to the device. That's the name, that's the vibe, periodt. 👑

---

🧾 SYNOPSIS 🧾

struct ti_sci_resource * devm_ti_sci_get_resource (const struct
       ti_sci_handle *handle , struct device *dev , u32 dev_id , u32 sub_type
       );

---

🎀 ARGUMENTS 🎀

• handle — TISCI handle. The main character you're handing over. 💅
• dev — device pointer to which the resource is assigned. Like, whose resource is this? This device's. 🫶
• dev_id — TISCI device id to which the resource is assigned. The id says which device it belongs to. 🔥
• sub_type — TISCI resource subytpe representing the resource. Yep, subytpe — spelling and all, bestie 💀

---

🌈 RETURN 🌈

Pointer to ti_sci_resource if all went well — else appropriate error pointer. So, success = cute pointer, failure = error pointer. Simple as that. 🎀

---

🔗 SEE ALSO 🔗

okay bestie, this cross-reference list is literally a whole group chat. Every single one is here:

• Kernel file ./drivers/firmware/ti_sci.c
• struct ti_sci_xfer(9)
• struct ti_sci_xfers_info(9)
• struct ti_sci_desc(9)
• struct ti_sci_irq(9)
• struct ti_sci_info(9)
• ti_sci_debug_show(9)
• ti_sci_debugfs_create(9)
• ti_sci_dump_header_dbg(9)
• ti_sci_rx_callback(9)
• ti_sci_get_one_xfer(9)
• ti_sci_put_one_xfer(9)
• ti_sci_do_xfer(9)
• ti_sci_cmd_get_revision(9)
• ti_sci_is_response_ack(9)
• ti_sci_set_device_state(9)
• ti_sci_get_device_state(9)
• ti_sci_cmd_get_device(9)
• ti_sci_cmd_get_device_exclusive(9)
• ti_sci_cmd_idle_device(9)
• ti_sci_cmd_idle_device_exclusive(9)
• ti_sci_cmd_put_device(9)
• ti_sci_cmd_dev_is_valid(9)
• ti_sci_cmd_dev_get_clcnt(9)
• ti_sci_cmd_dev_is_idle(9)
• ti_sci_cmd_dev_is_stop(9)
• ti_sci_cmd_dev_is_on(9)
• ti_sci_cmd_dev_is_trans(9)
• ti_sci_cmd_set_device_resets(9)
• ti_sci_cmd_get_device_resets(9)
• ti_sci_set_clock_state(9)
• ti_sci_cmd_get_clock_state(9)
• ti_sci_cmd_get_clock(9)
• ti_sci_cmd_idle_clock(9)
• ti_sci_cmd_put_clock(9)
• ti_sci_cmd_clk_is_auto(9)
• ti_sci_cmd_clk_is_on(9)
• ti_sci_cmd_clk_is_off(9)
• ti_sci_cmd_clk_set_parent(9)
• ti_sci_cmd_clk_get_parent(9)
• ti_sci_cmd_clk_get_num_parents(9)
• ti_sci_cmd_clk_get_match_freq(9)
• ti_sci_cmd_clk_set_freq(9)
• ti_sci_cmd_clk_get_freq(9)
• ti_sci_cmd_prepare_sleep(9)
• ti_sci_msg_cmd_query_fw_caps(9)
• ti_sci_cmd_set_io_isolation(9)
• ti_sci_msg_cmd_lpm_wake_reason(9)
• ti_sci_cmd_set_device_constraint(9)
• ti_sci_cmd_set_latency_constraint(9)
• ti_sci_cmd_lpm_abort(9)
• ti_sci_get_resource_range(9)
• ti_sci_cmd_get_resource_range(9)
• ti_sci_cmd_get_resource_range_from_shost(9)
• ti_sci_manage_irq(9)
• ti_sci_irq_hash(9)
• ti_sci_irq_equal(9)
• ti_sci_set_irq(9)
• ti_sci_free_irq(9)
• ti_sci_cmd_set_irq(9)
• ti_sci_cmd_set_event_map(9)
• ti_sci_cmd_free_irq(9)
• ti_sci_cmd_free_event_map(9)
• ti_sci_cmd_rm_ring_cfg(9)
• ti_sci_cmd_rm_psil_pair(9)
• ti_sci_cmd_rm_psil_unpair(9)
• ti_sci_cmd_rm_udmap_tx_ch_cfg(9)
• ti_sci_cmd_rm_udmap_rx_ch_cfg(9)
• ti_sci_cmd_rm_udmap_rx_flow_cfg(9)
• ti_sci_cmd_proc_request(9)
• ti_sci_cmd_proc_release(9)
• ti_sci_cmd_proc_handover(9)
• ti_sci_cmd_proc_set_config(9)
• ti_sci_cmd_proc_set_control(9)
• ti_sci_cmd_proc_get_status(9)
• ti_sci_get_handle(9)
• ti_sci_put_handle(9)
• devm_ti_sci_get_handle(9)
• ti_sci_get_by_phandle(9)
• devm_ti_sci_get_by_phandle(9)
• ti_sci_get_free_resource(9)
• ti_sci_release_resource(9)
• ti_sci_get_num_resources(9)
• devm_ti_sci_get_resource_sets(9)
• devm_ti_sci_get_of_resource(9)

---

anyway, source/version is ./drivers/firmware, date is October 2026, and the page is devm_ti_sci_get_resource(9) — mwah, bye bestie 🫶💖