STRUCT TI_SCI_MSG_RESP_QUERY_CLOCK_FREQ(9)
π struct ti_sci_msg_resp_query_clock_freq(9) π
okay so bestie, welcome to the Kernel API Manual β¨ β this little section is all about struct ti_sci_msg_resp_query_clock_freq, and it's literally the response you get back when you ask the TI SCI firmware "hey what's this clock running at?" ππ
πΈ NAME πΈ
struct ti_sci_msg_resp_query_clock_freq β the response to a clock frequency query, periodt π
π¦ SYNOPSIS π¦
struct ti_sci_msg_resp_query_clock_freq {
struct ti_sci_msg_hdr hdr;
u64 freq_hz;
};
like, that's the whole shape of it, no cap β¨
π Members π
hdrβ the generic header, aka the vibe check every TI SCI message starts with π«Άfreq_hzβ the frequency that is the best match, in Hz. bestie, best match β the firmware picks the closest one it's got π₯
π Description π
This struct is the response to request type TI_SCI_MSG_QUERY_CLOCK_FREQ π«
β οΈ NOTE: if the request cannot be satisfied, the message will be of type NACK. like, it's not gonna ghost you with a fake frequency β it straight-up NACKs. respect π
π SEE ALSO π
Kernel file ./drivers/firmware/ti_sci.h β go read it, iykyk π
And the whole friend group of structs, all of them, in this exact order because we don't skip anyone in this house π:
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_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)
sign-off time π this icon lives in ./drivers/firmware, dated October 2026 β that's the source and the date, bestie, written down so you never have to wonder π¦β¨ slay, go read some kernel headers π
π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms