ti_sci_cmd_...t_match_freq(9)

📦 version 7.3.1, in nixpkgs unstable

✨ NAME ✨

okay bestie, welcome to the ti_sci_cmd_...t_match_freq(9) page from the Kernel API Manual ✨

ti_sci_cmd_clk_get_match_freq — find a good match for frequency 💅 periodt.

🦋 SYNOPSIS 🦋

int ti_sci_cmd_clk_get_match_freq (const struct ti_sci_handle *handle ,
       u32 dev_id , u32 clk_id , u64 min_freq , u64 target_freq , u64 max_freq
       , u64 *match_freq );

🎀 ARGUMENTS 🎀

okay so here's the whole cast, no cap — every parameter matters, bestie 🫶

  • handle — pointer to the TI SCI handle.
  • dev_id — device identifier this request is for.
  • clk_id — clock identifier for the device for this request. Each device has its own set of clock inputs, and this indexes which clock input to modify.
  • min_freq — the minimum allowable frequency in Hz. This is the minimum allowable programmed frequency and does not account for clock tolerances and jitter.
  • target_freq — the target clock frequency in Hz. A frequency will be processed as close to this target frequency as possible.
  • max_freq — the maximum allowable frequency in Hz. This is the maximum allowable programmed frequency and does not account for clock tolerances and jitter.
  • match_freq — frequency match in Hz response.

💅 RETURN 💅

0 if all went well — slay — else it returns the appropriate error value 😭

🔥 SEE ALSO 🔥

Kernel file ./drivers/firmware/ti_sci.c is the main-character spot, and these (9) pages are the whole friend group — go say hi, iykyk 💖

mwah 💋 — source/version line: ./drivers/firmware, October 2026, page ti_sci_cmd_...t_match_freq(9). bye bestie! 🫶🎀
📦 where this page comes from