devm_get_clk_from_child(9)

📦 version 7.3.1, in nixpkgs unstable

💅 devm_get_clk_from_child — like, the manual page bestie

ok so welcome to the Kernel API Manual entry for devm_get_clk_from_child, the little function that's about to become your whole personality 🎀

✨ NAME ✨

devm_get_clk_from_child — lookup and obtain a managed reference to a clock producer from child node. yes that's the whole vibe: you look it up, you obtain it, and it's managed. iconic behaviour honestly 🫶

🌸 SYNOPSIS 🌸

struct clk * devm_get_clk_from_child (struct device *dev , struct device_node *np , const char *con_id );

that's it. that's the whole call. three args, one struct clk * back. slay 💅

🦋 ARGUMENTS 🦋

  • dev — the device that's acting as the clock "consumer". it's the one doing the consuming. main character energy, obviously.
  • np — pointer to the clock consumer node. like, the node node. the child node in question 👑
  • con_id — the clock consumer ID. the name-tag basically ✨

🔥 DESCRIPTION 🔥

ok so real talk: this function parses the clocks, and then it uses them to look up the struct clk from the registered list of clock providers — and it does that by using np and con_id. that's the whole lookup mechanism, no cap 🧚

and here's the part everyone's obsessed with: the clock will automatically be freed when the device is unbound from the bus. automatic cleanup?? we love a self-cleaning situation. that's the "managed" part of "managed reference" and it literally does the freeing for you so you don't have to 😭💖

ngl this is the actual selling point — no manual teardown, the devres machinery handles it when the device gets unbound from the bus. periodt.

⭐ SEE ALSO ⭐

it's giving "reference section went to the gym". every single one of these, in order, no skips 💀

ok that's the page!! this one lives out of ./include/linux and it's dated October 2026 — so like, mark your calendars bestie 🗓️💜 go free your clocks automatically, ily, bye 🫶✨

📦 where this page comes from