exynos_arm64_enable_bus_clk(9)
β¨ exynos_arm64_enable_bus_clk(9) β¨
okay so bestie, welcome to the Kernel API Manual β this one's a 9-section page and it's lowkey a little baddie π
πΈ NAME πΈ
exynos_arm64_enable_bus_clk β the function that enables the parent clock of a specified CMU. yes queen, that's the whole job, and she does it flawlessly π
π¦ SYNOPSIS π¦
int exynos_arm64_enable_bus_clk (struct device *dev , struct device_node
*np , const struct samsung_cmu_info *cmu );
look at her. three args, returns an int, const-correct on the cmu. main character energy ngl π
π ARGUMENTS π
devβ the device object π«Ά. Heads up though: this one may beNULLif this function is not being called from a platform driver probe function. so like,NULLis valid here, don't panic.npβ the CMU device tree node π³ β that's your node pointer.cmuβ the CMU data π¦, coming in as aconst struct samsung_cmu_info *because we're not touching it, we're just reading her vibe.
π DESCRIPTION π
So what does she actually do? She keeps the CMU parent clock running β and the reason is honestly so real: you need that parent clock alive for CMU registers access π₯. Like, no clock, no register poking. That's the whole deal, periodt.
β RETURN β
0on success π β slay, we're so back- a negative error code on failure π β not slay, but at least it's negative, which is how the kernel says "no"
π§ SEE ALSO π§
- Kernel file
./drivers/clk/samsung/clk-exynos-arm64.cπ β that's where the girlies live exynos_arm64_init_clocks(9)β¨exynos_arm64_register_cmu(9)πexynos_arm64_register_cmu_pm(9)π«
and that's the page!! π this iconic lil manual lives in ./drivers/clk/samsung and it's dated October 2026 β yes, future-dated, she's ahead of her time ππ ily, go enable those bus clocks bestie π«Ά
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms