STRUCT TI_SCI_MSG_RESP_GET_CLOCK_PARENT(9)
π struct ti_sci_msg_resp_get_clock_parent(9) π
okay so bestie, welcome to the Kernel API Manual β¨ this is the page for struct ti_sci_msg_resp_get_clock_parent, and yes the name is a whole mouthful but we're gonna get through it together, hand in hand π«Ά
πΈ NAME πΈ
struct ti_sci_msg_resp_get_clock_parent β the response struct that tells you which clock parent you're dealing with. literally that's her whole job π
β¨ SYNOPSIS β¨
struct ti_sci_msg_resp_get_clock_parent {
struct ti_sci_msg_hdr hdr;
u8 parent_id;
u32 parent_id_32;
};
look at her!! three members, zero drama, absolutely iconic π
π Members π
hdrβ the generic header, just your standard-issue header doing standard-issue header things π«parent_idβ the current clock parent. but bestie, listen: if this is set to255, the actual current parent ID is hiding in theparent_id_32field instead. so don't @ her, she's just a small field πparent_id_32β this is where the current clock parent lives ifparent_idis set to255. the big field for the big moments, no cap π₯
π¦ Description π¦
this struct is the response to TI_SCI_MSG_GET_CLOCK_PARENT. that's it, that's the vibe check, and she passed π
π SEE ALSO π
the whole squad, fr fr β go check them out in the kernel file ./drivers/firmware/ti_sci.h:
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_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)
okay that's the whole page, you ate that bestie π
β¨ and before you go β this lil masterpiece lives in ./drivers/firmware, dated October 2026, from the Kernel API Manual. mwah, study up, ily, bye πππ¦
π¦ 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