ti_sci_cmd_get_clock_state(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ti_sci_cmd_get_clock_state β€” straight out of the Kernel API Manual, bestie ✨

Okay so picture this: you're deep in the TI SCI firmware layer (./drivers/firmware/ti_sci.c, we'll get there) and you just need to know what a clock is doing. That's it. That's the whole vibe. This little helper is your girl πŸ’–


🌸 NAME 🌸

ti_sci_cmd_get_clock_state β€” the get-clock-state helper, no cap. It's giving "just tell me the state of this clock" energy and honestly? Iconic.


πŸŽ€ SYNOPSIS πŸŽ€

int ti_sci_cmd_get_clock_state (const struct ti_sci_handle *handle , u32 dev_id , u32 clk_id , u8 *programmed_state , u8 *current_state );

That's the whole signature, character for character, do not come for me 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • handle β€” pointer to the TI SCI handle. This is your main character, your entry pass to the whole SCI situation πŸ’…
  • dev_id β€” the device identifier this request is for. Whose clock are we snooping on? This one.
  • clk_id β€” the clock identifier for the device for this request. Lowkey important detail: each device has its own set of clock inputs, and this indexes which clock input to modify. Yes, "modify" β€” that's literally what the original says, I'm not gonna pretend otherwise πŸ™ˆ
  • programmed_state β€” the state requested for the clock to move to. Like, the state somebody asked for. The intended vibe.
  • current_state β€” the state the clock is currently in. The reality check. The vibe check, if you will ✨

⭐ RETURN ⭐

0 if all went well 😌 β€” otherwise it returns the appropriate error value 😭. So basically: zero is the slay, anything else is a "girl, check the error" moment.


πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/firmware/ti_sci.c β€” and literally the entire TI SCI extended family, because this function does not exist in isolation, bestie, it has connections πŸ‘‘

Like I said. Connections. 🧚


And that's the page, bestie β€” go read your clock states responsibly πŸ’œ

Sign-off time πŸŽ€ this one lives under ./drivers/firmware and it's dated October 2026, so yeah, it's got that cute little timestamp on it. Byeee ✨

πŸ“¦ where this page comes from