of_clk_parent_fill(9)

📦 version 7.3.1, in nixpkgs unstable

💅 of_clk_parent_fill(9) 💅

Okay bestie, so this is a page straight outta the Kernel API Manual — yes, the Kernel API Manual, we're literally in the big leagues now — and it's all about of_clk_parent_fill. It's a tiny little function with main character energy, and honestly? It ate. Let's get into it 🫶

✨ NAME ✨

of_clk_parent_fill — fill @parents with the names of @np's parents, and then hand you back the number of parents 💖

Like, that's the whole gig. It fills the array, it tells you how many it filled. No cap.

🦋 SYNOPSIS 🦋

int of_clk_parent_fill (struct device_node *np , const char **parents ,
       unsigned int size );

Look at her. Three args, returns an int. Simple, clean, iconic 👑

🎀 ARGUMENTS 🎀

  • np — the device node pointer that's associated with the clock provider. This is the node whose parents we're talking about, iykyk 🌸
  • parents — pointer to a char array that holds the parents' names. This is your output spot, bestie, so make sure it's got room 💅
  • size — the size of the parents array. Yes, you do have to tell it. Boundaries are healthy ✨

⭐ RETURN ⭐

It returns the number of parents for the clock node 🔥

That's it, that's the return. Literally just the count. Not the parents themselves — those went into your array. She's giving "I did the work, now here's the receipt" 💀

🌈 SEE ALSO 🌈

Okay this list is long long, like a group chat after a drama, but every single one is here because we don't do half-finished around here 💜

Fr fr go read a few of those if you wanna understand the whole clock vibe. of_clk_get_parent_count(9) is lowkey her cousin, so maybe start there 🧚

And that's the page, bestie! This lil gem lives under ./drivers/clk and was dated October 2026 — so yeah, she's from the future, obviously 💅 Slay, go write some clock code, and remember: fill your array, respect your size ✨🍓

📦 where this page comes from