_sci_clk_build(9)

🎀 NAME 🎀

_sci_clk_build — Gets a handle for an SCI clock. Yep bestie, this is the Kernel API Manual page for it, and we are getting into it ✨

---

💖 SYNOPSIS 💖

The whole signature, no edits, no cap:

int _sci_clk_build (struct sci_clk_provider *provider , struct sci_clk
*sci_clk );

---

🌸 ARGUMENTS 🌸

• provider — Handle to SCI clock provider. The plug, basically 🔌
• sci_clk — Handle to the SCI clock to populate. This is the one getting filled in 🫶

---

🦋 DESCRIPTION 🦋

Okay so here's the vibe: this gets a handle to an existing TI SCI hw clock, or it builds a new clock entry and registers it with the common clock framework. Iconic behavior honestly 👑

It's called from the common clock framework, when a corresponding of_clk_get call is executed, or recursively from itself when parsing parent clocks. So yes, it can call itself — recursion era 💫

Returns 0 on success, negative error code on failure. No cap: success is the happy little zero, failure gives you a negative error code 😭

fr fr, that return value matters. 0 = slay, negative = not slay.

---

🔥 SEE ALSO 🔥

Kernel file ./drivers/clk/keystone/sci-clk.c — yes, that exact path, and the whole friend group:

• struct sci_clk_provider(9)
• struct sci_clk(9)
• sci_clk_prepare(9)
• sci_clk_unprepare(9)
• sci_clk_is_prepared(9)
• sci_clk_recalc_rate(9)
• sci_clk_determine_rate(9)
• sci_clk_set_rate(9)
• sci_clk_get_parent(9)
• sci_clk_set_parent(9)
• sci_clk_get(9)
• ti_sci_clk_probe(9)
• ti_sci_clk_remove(9)

---

Signed, sealed, delivered by ./drivers/clk/keystone, dated October 2026 💅✨ Go off, kernel bestie 🌈💜