ti_sci_cmd_idle_clock(9)

📦 version 7.3.1, in nixpkgs unstable

💅 ti_sci_cmd_idle_clock(9) — from the Kernel API Manual, bestie 🎀

okay so picture this: it's a kernel API manual page, it's serving <purple>TI SCI</purple> realness, and this one function is literally the "please chill out, clock" button. Let's get into it ✨

🌸 NAME 🌸

ti_sci_cmd_idle_clock — idle a clock which is in our control. that's it. that's the whole vibe. 🫶

✨ SYNOPSIS ✨

int ti_sci_cmd_idle_clock (const struct ti_sci_handle *handle , u32
dev_id , u32 clk_id );

look at her. iconic signature. no notes. 👑

🦋 ARGUMENTS 🦋

  • handle — pointer to the TI SCI handle. this is your VIP pass to the whole TI SCI situation, don't lose it 🙈
  • dev_id — the device identifier this request is for. which device are we talking to? this one. 🎯
  • clk_id — the clock identifier for the device for this request. and listen: each device has its own set of clock inputs (fr fr, they don't share), so this indexes which clock input to modify. it's giving "pick your fighter" energy 🕹️

💀 NOTE 💀

this clock must have been requested by get_clock previously. like, previously previously. no sneaky idling a clock you never asked for, bestie, that's not the move 😭

🌈 RETURN 🌈

0 if all went well — slay, we love a zero 🎉 — else it returns the appropriate error value. read that error, don't ignore it, i'm begging 🥺

🔥 SEE ALSO 🔥

okay this part is a whole friend group, everybody's here, it's a party 🎊 starting with the kernel file:

Kernel file ./drivers/firmware/ti_sci.c

then the structs and the entire extended fam:

like i said. full party. everyone came. 💜

and that's the page!! sourced from ./drivers/firmware, dated October 2026 — okurrr, go idle some clocks responsibly, mwah 💋✨

📦 where this page comes from