ti_sci_cmd_get_clock(9)

📦 version 7.3.1, in nixpkgs unstable

🎀 NAME 🎀

okay so bestie, this is ti_sci_cmd_get_clock(9) from the Kernel API Manual — and the whole vibe is Get control of a clock from TI SCI. yes, it's giving firmware-core main character energy. 💅

✨ SYNOPSIS ✨

int ti_sci_cmd_get_clock (const struct ti_sci_handle *handle , u32
dev_id , u32 clk_id , bool needs_ssc , bool can_change_freq , bool
enable_input_term );

🦋 ARGUMENTS 🦋

  • handle — pointer to TI SCI handle. that's your golden ticket into the TI SCI world. 🎟️
  • dev_id — Device identifier this request is for. literally the “who is this for” of the whole thing. 👑
  • clk_id — Clock identifier for the device for this request. Each device has its own set of clock inputs. This indexes which clock input to modify. so yeah, it picks the exact clock input bestie. 🕰️
  • needs_ssc — the original page gives no extra description here; it's just listed as a bool. no invented lore, periodt. 🫶
  • can_change_freq — same deal: no description on the page, just a bool. we are not making up extra facts, ngl. 💀
  • enable_input_term — also no description in the source; it's a bool and that's all we get. iconic minimalism, honestly. ✨

🌸 RETURN 🌸

0 if all went well, else returns appropriate error value. that's the whole mood: slay if it works, error value if it doesn't. 😭

🌈 SEE ALSO 🌈

Kernel file: ./drivers/firmware/ti_sci.c — that's the source-file bestie! and the whole squad is here:

made with 💖 from the ./drivers/firmware source/version corner, dated October 2026, for ti_sci_cmd_get_clock(9) — mwah, bye bestie! 🎀✨

📦 where this page comes from