STRUCT TI_SCI_MSG_REQ_GET_DEVICE_STATE(9)

💅 NAME

struct ti_sci_msg_req_get_device_state — the literal request-to-get-device struct, bestie. It's the lil message you send when you want the device state and you're not about to guess. This is page struct ti_sc...device_state(9) from the Kernel API Manual, and yes we are reading it together, grab a snack 🍓

---

✨ SYNOPSIS

struct ti_sci_msg_req_get_device_state {
    struct ti_sci_msg_hdr hdr;
    u32 id;
 };

That's the whole shape of it. Two fields. Iconic, minimal, no notes 👑

---

🫶 Members

• hdr — the generic header, aka the boring-but-essential envelope every message rides in. It's giving "don't talk to me before my header" energy ✨
• id — the Device Identifier. This is how you tell it WHICH device you're asking about. No id, no vibe check. Literally the whole point fr fr 🎀

---

🔥 Description

Okay so the tea ☕ — the request type here is TI_SCI_MSG_GET_DEVICE_STATE, and what comes back is the responded device state information. That's it, that's the whole plot. You ask, the state info responds. Simple as. Obsessed with the efficiency tbh 💅

ngl this struct is a request — the answer is a whole other struct (peep the SEE ALSO, we got you) so don't be out here expecting the state to live in here. 🙈

---

🌈 SEE ALSO

The kernel file to go stare at is ./drivers/firmware/ti_sci.h — that's where all these live, and lowkey it's a whole family reunion in there 🧚

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

Like I said. Whole family. Read them all, iykyk 🔥

---

okay that's the whole page, mwah 💖 This one comes at you from ./drivers/firmware, dated October 2026, and it's filed under struct ti_sc...device_state(9) — go forth and query your device states responsibly, bestie 🦋🌸