STRUCT TI_SCI_MSG_REQ_PROC_RELEASE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ‘‘ struct ti_sci_msg_req_proc_release β€” Kernel API Manual, bestie edition

okay so this is a page from the Kernel API Manual, and it's about struct ti_sci_msg_req_proc_release β€” the little message struct you send when you want a processor to be, like, let go. free. released into the world πŸ¦‹


✨ NAME ✨

struct ti_sci_msg_req_proc_release β€” Release a processor. that's it, that's the whole vibe. it's giving "letting go" energy πŸ’…


🌸 SYNOPSIS 🌸

here's the whole shape of it, no cap:

struct ti_sci_msg_req_proc_release {
    struct ti_sci_msg_hdr hdr;
    u8 processor_id;
 };

like, that's genuinely it. two fields. she's simple, she's iconic, she does her job πŸŽ€


πŸŽ€ Members πŸŽ€

  • hdr β€” Generic Header. the standard little intro every one of these messages shows up with, iykyk.
  • processor_id β€” ID of processor being released. literally just which processor we're setting free πŸ”₯ it's a u8, so keep it cute and in range.

πŸ’œ Description πŸ’œ

okay so the tea β˜• β€” the request type for this one is TI_SCI_MSG_PROC_RELEASE, and the response you get back is a generic ACK/NACK message. so like, yes/no, slay/fail, that's the whole reply. no extra lore, no bonus data, just vibes and a verdict 🫢


🌈 SEE ALSO 🌈

bestie there are SO many siblings, buckle up β€” the kernel file ./drivers/firmware/ti_sci.h and honestly the entire extended family:

  • 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_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 I said. huge family. every single one of them is invited to the group chat πŸ’€βœ¨


🧚 friendly reminder: the header is the generic one (struct ti_sci_msg_hdr), and the whole request is literally just that header plus one u8. don't overthink her.

okay that's the whole page, ily, go release some processors responsibly πŸ’– this was struct ti_sc...proc_release(9) from ./drivers/firmware, dated October 2026, and she ate. periodt. πŸ‘‘β­

πŸ“¦ where this page comes from