STRUCT TI_SCI_MSG_REQ_PROC_HANDOVER(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct ti_sci_msg_req_proc_handover(9) β€” like, the Kernel API Manual page, section 9, bestie ✨

okay so you opened a kernel API manual page, and honestly? good for you 🫢. This one lives in the Kernel API Manual, section 9, and it's literally all about handing a whole processor over to a host. main character energy fr fr πŸ‘‘


🌸 NAME 🌸

struct ti_sci_msg_req_proc_handover β€” Handover a processor to a host πŸ’«

(yeah that's the whole name section, she's short and to the point, we respect her)


✨ SYNOPSIS ✨

Here's the struct, laid out all pretty, copy it exactly please:

struct ti_sci_msg_req_proc_handover {
    struct ti_sci_msg_hdr hdr;
    u8 processor_id;
    u8 host_id;
 };

Like, three members, no drama, we love a minimal queen πŸŽ€


πŸ’– MEMBERS πŸ’–

  • hdr β€” the Generic Header. every one of these structs has one, it's giving "everyone gets a participation trophy" but make it protocol πŸ†
  • processor_id β€” ID of processor being handed over. yes, which processor. this is the who πŸ‘ˆ
  • host_id β€” Host ID the control needs to be transferred to. this is the where to, the destination, the new home 🏑

πŸ”₯ Description πŸ”₯

so the request type for this whole vibe is TI_SCI_MSG_PROC_HANDOVER, and the response? a generic ACK/NACK message. that's it. no fancy payload, no extra lore, just "yep got it" or "nope" πŸ˜­πŸ’€


πŸ‘‘ SEE ALSO πŸ‘‘

okay bestie, buckle up, because this list is long and we are NOT skipping a single one of these, no cap. The kernel file is ./drivers/firmware/ti_sci.h and it's friends with literally everyone:

  • 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_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_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, the whole friend group showed up to the group chat, and honestly? obsessed πŸ’…πŸ¦‹


so yeah, that's the page! you're officially a ti_sci processor-handover understander 🌈⭐

and for the cute sign-off: this little beauty is sourced from ./drivers/firmware and dated October 2026 πŸ—“οΈπŸ’œ β€” go forth and hand over those processors responsibly, bestie πŸŽ€

πŸ“¦ where this page comes from