device_get_named_child_node(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

Okay bestie, welcome to the Kernel API Manual entry for device_get_named_child_node(9). It returns the first matching named child node handle. That's the whole assignment, and it ate. πŸ’…


✨ SYNOPSIS ✨

struct fwnode_handle * device_get_named_child_node (const struct device
       *dev , const char *childname );

πŸŽ€ ARGUMENTS πŸŽ€

  • dev β€” the Device you're finding the named child node for.
  • childname β€” the String you're matching against the child node name.

πŸ¦‹ DESCRIPTION πŸ¦‹

So here's the one thing you literally cannot skip, bestie: the caller is responsible for calling fwnode_handle_put on the returned fwnode pointer. That's the responsibility, and it's giving main character energy. Don't ghost it, fr fr. 🫢


πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/base/property.c, plus all the friends in the group chat:


xoxo πŸ’‹ this page is from source/version ./drivers/base, dated October 2026, and it's the device_get_named_child_node(9) manual page. periodt. 🫢✨

πŸ“¦ where this page comes from