STRUCT TI_SCI_MSG_RESP_GET_CLOCK_STATE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay so bestie, welcome to the Kernel API Manual page for struct ti_sci_msg_resp_get_clock_state β€” header abbreviation struct ti_sc..._clock_state(9) β€” and it's giving β€œclock state response struct” main character energy βœ¨πŸ’….

🌸 NAME 🌸

struct ti_sci_msg_resp_get_clock_state β€” Response to get clock state. That's the name, no cap 🫢.

✨ SYNOPSIS ✨

okay so here's the literal struct, bestie β€” keep every character exactly as shown:

       struct ti_sci_msg_resp_get_clock_state {
           struct ti_sci_msg_hdr hdr;
           u8 programmed_state;
         #define MSG_CLOCK_HW_STATE_NOT_READY    0;
         #define MSG_CLOCK_HW_STATE_READY        1;
           u8 current_state;
        };

πŸŽ€ Members πŸŽ€

  • hdr β€” Generic Header. The little generic header bestie at the top πŸ’«.
  • programmed_state β€” Any programmed state of the clock. This is one of MSG_CLOCK_SW_STATE* values. (Yes, MSG_CLOCK_SW_STATE* β€” don't come for me, that's literally what it says 😭.)
  • current_state β€” Current state of the clock. This is one of:
    • MSG_CLOCK_HW_STATE_NOT_READY: Clock is not ready
    • MSG_CLOCK_HW_STATE_READY: Clock is ready
The synopsis defines those two as 0 and 1, respectively β€” MSG_CLOCK_HW_STATE_NOT_READY = 0; MSG_CLOCK_HW_STATE_READY = 1. Periodt πŸ’….

πŸ¦‹ Description πŸ¦‹

This struct is literally the response to TI_SCI_MSG_GET_CLOCK_STATE. Like, that's the whole description, bestie β€” no extra lore, no side quests 🌈.

πŸ”₯ SEE ALSO πŸ”₯

Kernel file: ./drivers/firmware/ti_sci.h β€” go read the source, iykyk πŸ“–βœ¨.

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

bye bestie πŸ’– source/version footer: ./drivers/firmware; date: October 2026; footer title: struct ti_sc..._clock_state(9) β€” that's the whole footer, periodt βœ¨πŸŽ€

πŸ“¦ where this page comes from