fwnode_get_named_child_node(9)

📦 version 7.3.1, in nixpkgs unstable

🦋 fwnode_get_named_child_node(9) — from the Kernel API Manual, bestie ✨

Okay so this is a page straight outta the Kernel API Manual, and honestly? It's short, it's sweet, it's giving "tiny function, big responsibility". Let's get into it 💅

✨ NAME ✨

fwnode_get_named_child_node — gets you the first matching named child node handle 🌸 Like, the very first one it finds with that name. Not the second, not the third. The first. Periodt.

🎀 SYNOPSIS 🎀

struct fwnode_handle * fwnode_get_named_child_node (const struct fwnode_handle *fwnode , const char *childname );

Yes bestie, it spits back a struct fwnode_handle * 🫶

💖 ARGUMENTS 💖

  • fwnode — the firmware node you're doing the search in 🔍 This is the one whose children we're checking. Main character energy, honestly.
  • childname — the string you're matching against the child node's name 🎯 Literally just the name you're looking for.

🧚 DESCRIPTION 🧚

Okay so the one thing you cannot forget, and I mean it, no cap:

The caller is responsible for calling fwnode_handle_put on the returned fwnode pointer. 🔥

Like — you own the cleanup, bestie. If you take the handle and never put it back, that's a leak and the kernel will be side-eyeing you 😭 Don't do that to yourself.

🌈 SEE ALSO 🌈

So this lives in the kernel file ./drivers/base/property.c, and the whole friend group is huge. Here's literally everyone iykyk 💜

And that's the whole page, bestie! 💅 This one comes to you from ./drivers/base, dated October 2026, and it's the fwnode_get_named_child_node(9) page — go get that named child node and remember to put the handle back, I'm begging 🫶✨🎀

📦 where this page comes from