exynos_arm64_enable_bus_clk(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ 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 be NULL if this function is not being called from a platform driver probe function. so like, NULL is valid here, don't panic.
  • np β€” the CMU device tree node 🌳 β€” that's your node pointer.
  • cmu β€” the CMU data πŸ“¦, coming in as a const 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 ⭐

  • 0 on 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 🧚


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