STRUCT TI_SCI_MSG_RESP_GET_CLOCK_NUM_PARENTS(9)

🦋 struct ti_sci_msg_resp_get_clock_num_parents(9) 🦋

okay bestie, welcome to the Kernel API Manual 💖 this is the page for the struct that handles the “how many clock parents are there?” response. It’s giving very specific firmware-message main character energy, and we’re gonna get into all of it. ✨

🌸 NAME 🌸

struct ti_sci_msg_resp_get_clock_num_parents — response for get clk parents, no cap. 🎀

✨ SYNOPSIS ✨

bestie, here’s the struct layout, literally:

struct ti_sci_msg_resp_get_clock_num_parents {
    struct ti_sci_msg_hdr hdr;
    u8 num_parents;
    u32 num_parents_32;
};

🫶 Members 🫶

• hdr — Generic header. It’s the standard intro bit, the “hey bestie” of the struct. 💅
• num_parents — Number of clock parents. If set to 255, the actual number of parents is stored into the num_parents_32 field instead. So yeah, 255 is the little “look over there” value, and the real count is chilling in num_parents_32. 👀
• num_parents_32 — Number of clock parents if the num_parents field is set to 255. That’s the whole vibe. 🦋

💅 Description 💅

Response to TI_SCI_MSG_GET_NUM_CLOCK_PARENTS. That’s it, that’s the tea — it’s the reply struct for that message. 🌈

👑 SEE ALSO 👑

okay so here’s the full crew from the kernel file ./drivers/firmware/ti_sci.h, every single one, no skips, periodt:

• Kernel file ./drivers/firmware/ti_sci.h — home base for this whole struct situation. 🏠
• 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_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)

and that’s the whole page, bestie 💖 cute little sign-off from ./drivers/firmware, dated October 2026, with the footer name struct ti_sc..._num_parents(9). slay, goodbye, go read some kernel headers. 🎀🔥