ti_sci_clk_probe(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ti_sci_clk_probe πŸ’…

okay so this is a page straight out of the Kernel API Manual, and it's about one very specific little function, but trust me bestie it's lowkey the main character of the TI SCI clock driver's origin story ✨


πŸŽ€ NAME πŸŽ€

ti_sci_clk_probe β€” the probe function for the TI SCI clock driver. that's it, that's the job description πŸ’–


🌸 SYNOPSIS 🌸

int ti_sci_clk_probe (struct platform_device *pdev );

like, it takes one thing and gives you back an int. simple. elegant. iconic.


πŸ¦‹ ARGUMENTS πŸ¦‹

  • pdev β€” the platform device pointer that's about to get probed. yes, that pdev. the one being probed. it's giving "here's the device, do your thing" 🫢

⭐ DESCRIPTION ⭐

so what does it actually do? buckle up:

this function probes the TI SCI clock device πŸ•°οΈ. it allocates a brand-new clock provider and registers that provider with the common clock framework β€” like introducing your new friend to the group chat and hoping everyone gets along fr fr.

it also applies any required flags to the clocks it identifies, using clock lists that come straight from DT (device tree, iykyk 🌈).

and the return situation? returns 0 for success πŸ’š, or a negative error value for failure 😭. no in-between, no "maybe", that's just how it is.

ngl if you get a negative number back, something did NOT slay. check your flags and your DT lists bestie πŸ’€

πŸ‘‘ SEE ALSO πŸ‘‘

the whole squad, no cap:

every single one of them, exactly as named, go read them πŸ’œ


and that's the page!! mwah πŸ’‹ it lives under ./drivers/clk/keystone, it's dated October 2026, and it's part of that same Kernel API Manual we mentioned at the top. slay, bye πŸ§šβ€β™€οΈβœ¨

πŸ“¦ where this page comes from