of_get_next_available_child(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ of_get_next_available_child β€” Kernel API Manual ✨

okay so bestie, this is the of_get_next_available_child(9) page from the Kernel API Manual, and we are about to vibe-check a very specific little kernel helper πŸ¦‹. No cap, it’s giving β€œfind me the next available child node” energy, and we’re gonna keep every detail intact.


πŸ’– NAME πŸ’–

of_get_next_available_child β€” find the next available child node πŸ‘‘. That’s the whole assignment, periodt.

🌸 SYNOPSIS 🌸

struct device_node * of_get_next_available_child (const struct
       device_node *node , struct device_node *prev );

πŸŽ€ ARGUMENTS πŸŽ€

  • node β€” parent node. This is the parent node, iykyk β€” the one whose children we’re checking πŸ’….
  • prev β€” previous child of the parent node, or NULL to get first. Pass NULL when you want the first one, bestie ✨.

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so this function is literally of_get_next_child energy, except it automatically skips any disabled nodes (i.e. status = "disabled"). So if a node is disabled, it’s not the one β€” the function moves right past it, no dramatic exit needed πŸ’€.

🌈 SEE ALSO 🌈

Kernel file ./drivers/of/base.c is where this lives, and these are the related pages in the group chat πŸ‘€:


mwah πŸ’‹ β€” source/version: ./drivers/of, dated October 2026, for the of_get_next_available_child(9) page. Stay slay, and may your child nodes always be available 🫢✨

πŸ“¦ where this page comes from