STRUCT TI_SCI_MSG_RESP_GET_CLOCK_FREQ(9)

💖 struct ti_sci_msg_resp_get_clock_freq(9) 💖

okay so bestie, welcome to the Kernel API Manual — this is a whole page about the reply that comes back when you ask a clock "hey girl what's your frequency rn" 🕐✨ the struct is called struct ti_sci_msg_resp_get_clock_freq and it's literally the answer to a clock frequency request. no cap.

---

🌸 NAME 🌸

struct ti_sci_msg_resp_get_clock_freq — the Response of clock frequency request 🎀

---

✨ SYNOPSIS ✨

struct ti_sci_msg_resp_get_clock_freq {
    struct ti_sci_msg_hdr hdr;
    u64 freq_hz;
 };

---

🦋 Members 🦋

• hdr — the Generic Header, the little intro card every one of these messages carries 💅
• freq_hz — the Frequency that the clock is currently on, in Hz. like, the actual number you came for 🫶

---

💜 Description 💜

this struct is the Response to request type TI_SCI_MSG_GET_CLOCK_FREQ. so when something sends that request type, this is what bounces back at you. iconic behaviour honestly 🌈

---

👑 SEE ALSO 👑

Kernel file ./drivers/firmware/ti_sci.h and all these besties:

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

---

ngl that's a lot of structs and I love that for them 💀 every single one kept, fr fr — not me gatekeeping any 🍓

---

and that's the whole page bestie, mwah 💋 this cutie lives in ./drivers/firmware, dated October 2026, and the manual it belongs to is the Kernel API Manual — the header up top was just struct ti_s...t_clock_freq(9) doing its little truncation thing, and the footer was ./drivers/firmware + October 2026 + struct ti_s...t_clock_freq(9) again 💖 slay, go read some clock frequencies 🌟