STRUCT TI_SCI_MSG_RESP_GET_CLOCK_PARENT(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– 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 to 255, the actual current parent ID is hiding in the parent_id_32 field instead. so don't @ her, she's just a small field πŸ™ˆ
  • parent_id_32 β€” this is where the current clock parent lives if parent_id is set to 255. 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