ti_sci_cmd_proc_request(9)

💅 ti_sci_cmd_proc_request — from the Kernel API Manual ✨

okay bestie, so this page is literally about one function from the Kernel API Manual, and it's giving "tiny function, big responsibilities" energy. It's ti_sci_cmd_proc_request, and no cap, it's the one that goes and requests a physical processor control. That's the whole vibe. 🫶

---

🌸 NAME 🌸

ti_sci_cmd_proc_request — the command that requests a physical processor control. that's it, that's the function, and honestly? iconic. 👑

---

🎀 SYNOPSIS 🎀

int ti_sci_cmd_proc_request (const struct ti_sci_handle *handle , u8
proc_id );

like, look at her. returns an int, takes two things, does her little job. main character energy fr fr. ✨

---

🦋 ARGUMENTS 🦋

• handle — pointer to the TI SCI handle. yeah, the whole handle. you gotta hand her the keys before she can do anything 🔑
• proc_id — the processor ID this request is for. so like, which processor are we requesting? that one. u8. keep it cute 💖

---

🍓 RETURN 🍓

0 if all went well 🌈 — otherwise it returns the appropriate error value, and you get to have feelings about that. 😭

ngl bestie, always check the return. 0 is the slay outcome, anything else means go read the error. no skipping your vibe check. 💅

---

💜 SEE ALSO 💜

so there's a lot of friends in this group chat, and we're not leaving a single one out, periodt. first up, the kernel file itself: ./drivers/firmware/ti_sci.c — and then the whole crew:

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_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), devm_ti_sci_get_resource(9).

like… the way she knows everybody? obsessed. 🧚 iykyk.

---

okay real talk bestie — ti_sci_cmd_proc_request sits on the request side of the processor story, and the rest of the proc squad (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)) lives in that SEE ALSO list up there. that's the whole page, and we did not skip a single crumb of it. 💅

<div align="center">🌸 🦋 🎀 ✨ 💖 ✨ 🎀 🦋 🌸</div>

so that's the whole read, bestie. shoutout to ./drivers/firmware for being the home of this one, dated October 2026, and it's all filed under ti_sci_cmd_proc_request(9) — go forth and request your processor, and remember: check that return value, drink water, and slay. 🔥👑🫶