STRUCT TI_SCI_MSG_RESP_GET_STATUS(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct ti_sci_msg_resp_get_status(9) πŸ’…

okay so welcome to the Kernel API Manual, bestie β€” this page is all about struct ti_sci_msg_resp_get_status, and it is lowkey the main character of processor boot status responses. 🫢


🌸 NAME 🌸

struct ti_sci_msg_resp_get_status β€” Processor boot status response


✨ SYNOPSIS ✨

struct ti_sci_msg_resp_get_status {
    struct ti_sci_msg_hdr hdr;
    u8 processor_id;
    u32 bootvector_low;
    u32 bootvector_high;
    u32 config_flags;
    u32 control_flags;
    u32 status_flags;
};

πŸŽ€ Members πŸŽ€

  • hdr β€” Generic Header. Yep, the standard header bestie, no cap.
  • processor_id β€” ID of processor whose status is returned. iykyk, it tells you which processor's status is being handed back.
  • bootvector_low β€” Lower 32 bit address (Little Endian) of boot vector. The low half, little-endian, literally.
  • bootvector_high β€” Higher 32 bit address (Little Endian) of boot vector. The high half, also little-endian, slay.
  • config_flags β€” Optional Processor specific Config Flags set currently. The optional, processor-specific config flags that are currently set.
  • control_flags β€” Optional Processor specific Control Flags set currently. Same vibe, but control flags, and they're the optional processor-specific ones currently set.
  • status_flags β€” Optional Processor specific Status Flags set currently. The optional, processor-specific status flags currently set. Periodt.

πŸ’… Description πŸ’…

It's the response structure to a TI_SCI_MSG_GET_STATUS request. That's the whole lore, bestie β€” request goes out, this struct comes back. πŸ’–


πŸ¦‹ SEE ALSO πŸ¦‹

All of these live in the kernel file ./drivers/firmware/ti_sci.h, and honestly the friend group is huge:

  • 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_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)

okay that's the page!! source spot: ./drivers/firmware, dated October 2026, and the footer vibe is still struct ti_s...p_get_status(9) β€” mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from