STRUCT TI_SCI_MSG_REQ_GET_STATUS(9)

💅 NAME 💅

struct ti_sci_msg_req_get_status — the little "hey, is that processor awake yet??" request, bestie. Processor boot status request, that's the whole vibe. 🫶

✨ SYNOPSIS ✨

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

🎀 MEMBERS 🎀

• hdr — the Generic Header, aka the standard envelope every message rolls with. It's giving main character energy but in a supporting-role way, yk? 💌
• processor_id — the ID of the processor whose status you're asking about. Like, which specific CPU are we checking up on. Lowkey the whole point. 👑

🦋 DESCRIPTION 🦋

So the request type here is TI_SCI_MSG_GET_STATUS, and the response back is an appropriate message — or a NACK if the firmware simply can't satisfy your request. Not every ask gets a yes, no cap. 😭

🌈 SEE ALSO 🌈

Kernel file ./drivers/firmware/ti_sci.h — and honestly, the whole friend group shows up here, so let's list them all, no skipping, we don't do that here 💖:

• 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_resp_get_status(9)

okay that's the whole thing, you're officially educated ✨ this masterpiece lives in ./drivers/firmware, dated October 2026, and the page itself is struct ti_sc...q_get_status(9) — mwah, slay, periodt 💅🎀