STRUCT TI_SCI_CLK_OPS(9)

✨ struct ti_sci_clk_ops(9) ✨

okay so bestie, welcome to the Kernel API Manual 💅 this is the whole entire vibe of struct ti_sci_clk_ops — the clock control operations struct. it's giving "let me manage your clocks for you" energy, and honestly? iconic.

---

🌸 NAME 🌸

struct ti_sci_clk_ops — Clock control operations 🕐✨

---

🦋 SYNOPSIS 🦋

bestie. look at this struct. it's a whole menu of function pointers and it is lowkey a lot, but we're gonna get through it together 🫶

struct ti_sci_clk_ops {
    int (*get_clock)(const struct ti_sci_handle *handle, u32 did, u32 cid, bool needs_ssc, bool can_change_freq, bool enable_input_term);
    int (*idle_clock)(const struct ti_sci_handle *handle, u32 did, u32 cid);
    int (*put_clock)(const struct ti_sci_handle *handle, u32 did, u32 cid);
    int (*is_auto)(const struct ti_sci_handle *handle, u32 did, u32 cid, bool *req_state);
    int (*is_on)(const struct ti_sci_handle *handle, u32 did, u32 cid, bool *req_state, bool *current_state);
    int (*is_off)(const struct ti_sci_handle *handle, u32 did, u32 cid, bool *req_state, bool *current_state);
    int (*set_parent)(const struct ti_sci_handle *handle, u32 did, u32 cid, u32 parent_id);
    int (*get_parent)(const struct ti_sci_handle *handle, u32 did, u32 cid, u32 *parent_id);
    int (*get_num_parents)(const struct ti_sci_handle *handle, u32 did, u32 cid, u32 *num_parents);
    int (*get_best_match_freq)(const struct ti_sci_handle *handle, u32 did, u32 cid, u64 min_freq, u64 target_freq, u64 max_freq, u64 *match_freq);
    int (*set_freq)(const struct ti_sci_handle *handle, u32 did, u32 cid, u64 min_freq, u64 target_freq, u64 max_freq);
    int (*get_freq)(const struct ti_sci_handle *handle, u32 did, u32 cid, u64 *current_freq);
 };

---

💠 MEMBERS 💠

🕐 get_clock

Request for activation of clock and manage by processor — literally the "hey bestie, wake up" call for your clock.

• needs_ssc: 'true' if Spread Spectrum clock is desired.
• can_change_freq: 'true' if frequency change is desired.
• enable_input_term: 'true' if input termination is desired.

😴 idle_clock

Request for Idling a clock managed by processor. nap time fr fr.

🫳 put_clock

Release the clock to be auto managed by TISCI — letting go and letting the firmware take the wheel ✨

🤖 is_auto

Is the clock being auto managed — vibe check on who's actually in charge here.

• req_state: state indicating if the clock is auto managed.

🟢 is_on

Is the clock ON — the moment of truth.

• req_state: if the clock is requested to be forced ON.
• current_state: if the clock is currently ON.

🔴 is_off

Is the clock OFF — the opposite moment of truth.

• req_state: if the clock is requested to be forced OFF.
• current_state: if the clock is currently Gated.

👑 set_parent

Set the clock source of a specific device clock — choosing your clock's main character ancestor.

• parent_id: Parent clock identifier to set.

🔍 get_parent

Get the current clock source of a specific device clock — finding out who your clock's parent actually is.

• parent_id: Parent clock identifier which is the parent.

🧮 get_num_parents

Get the number of parents of the current clock source — counting the whole family tree.

• num_parents: returns the number of parent clocks.

🎯 get_best_match_freq

Find a best matching frequency for a frequency range. matchmaking, but for clock speeds 💘

• match_freq: Best matching frequency in Hz.

⚡ set_freq

Set the Clock frequency.

📏 get_freq

Get the Clock frequency.

• current_freq: Frequency in Hz that the clock is at.

---

💅 NOTE 💅

okay so for ALL of these functions, the following parameters are generic in nature — they show up everywhere, so memorize the squad 🫶

• -handle — Pointer to TISCI handle as retrieved by *ti_sci_get_handle
• -did — Device identifier this request is for
• -cid — Clock identifier for the device for this request. Each device has it's own set of clock inputs. 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.

Request for the clock — NOTE: the client MUST maintain integrity of usage count by balancing get_clock with put_clock. No refcounting is managed by driver for that purpose. not me stressing this but fr fr, balance them or you WILL have a bad time 😭

---

🌈 SEE ALSO 🌈

Kernel file ./include/linux/soc/ti/ti_sci_protocol.h — go read it, iykyk 🧚

• struct ti_sci_version_info(9)
• struct ti_sci_core_ops(9)
• struct ti_sci_dev_ops(9)
• struct ti_sci_pm_ops(9)
• struct ti_sci_resource_desc(9)
• struct ti_sci_rm_core_ops(9)
• struct ti_sci_rm_irq_ops(9)
• struct ti_sci_msg_rm_ring_cfg(9)
• struct ti_sci_rm_ringacc_ops(9)
• struct ti_sci_rm_psil_ops(9)
• struct ti_sci_rm_udmap_ops(9)
• struct ti_sci_proc_ops(9)
• struct ti_sci_ops(9)
• struct ti_sci_handle(9)
• struct ti_sci_resource(9)

---

💖 that's the whole page bestie 💖 brought to you from ./include/linux/soc/ti, dated October 2026, and yes the page is literally titled struct ti_sci_clk_ops(9) because we keep it consistent 👑 slay, go manage some clocks, periodt ✨🎀🦋