STRUCT TI_SCI_MSG_REQ_REBOOT(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

struct ti_sci_msg_req_reboot β€” Reboot the SoC 😭πŸ”₯

Okay bestie, welcome to the Kernel API Manual! We’re looking at struct ti_sci_msg_req_reboot, and it’s lowkey giving β€œtiny struct, major main-character energy” πŸ’…βœ¨

🌸 SYNOPSIS 🌸

struct ti_sci_msg_req_reboot {
    struct ti_sci_msg_hdr hdr;
};

πŸŽ€ Members πŸŽ€

  • hdr β€” Generic Header. That’s the whole member list, and honestly? Obsessed with the minimalism 🫢

πŸ¦‹ Description πŸ¦‹

The request type is TI_SCI_MSG_SYS_RESET, and it gets responded to with a generic ACK/NACK message. Periodt: that’s the entire description vibe β€” reboot request goes out, generic ACK/NACK comes back, no cap πŸ’€βœ¨

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file: ./drivers/firmware/ti_sci.h β€” plus all these struct besties, fr fr:

  • struct ti_sci_msg_hdr(9)
  • struct ti_sci_msg_resp_version(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_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)

Signed off with πŸ’– from the ./drivers/firmware source, dated October 2026, living in the struct ti_sc...g_req_reboot(9) footer era β€” bye bestie! πŸ’…βœ¨

πŸ“¦ where this page comes from