overlay_get_target_phandle(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

overlay_get_target_phandle β€” retrieves the target phandle of a fragment. Welcome to the overlay_get_target_phandle(9) page from the Kernel API Manual, bestie β€” yes, we're literally in kernel device-tree-overlay land and it's giving main character energy. πŸŽ€


🌸 SYNOPSIS 🌸

The whole call is literally this:

uint32_t overlay_get_target_phandle (const void *fdto , int fragment );

πŸ¦‹ ARGUMENTS πŸ¦‹

Two arguments, both iconic in their own way:

  • fdto β€” pointer to the device tree overlay blob 🫢
  • fragment β€” node offset of the fragment in the overlay ✨

πŸŽ€ DESCRIPTION πŸŽ€

Okay so overlay_get_target_phandle retrieves the target phandle of an overlay fragment when that fragment uses a phandle (the target property) instead of a path (the target-path property). That's the whole vibe β€” no cap, it's specifically about the target property versus the target-path property. πŸ’…


πŸ’… RETURN πŸ’…

It's giving three possible returns, bestie:

  • the phandle pointed by the target property πŸ‘‘
  • 0, if the phandle was not found
  • -1, if the phandle was malformed 😭

🌈 SEE ALSO 🌈

Kernel file first, because the source is right there:

  • Kernel file ./scripts/dtc/libfdt/fdt_overlay.c

And now the whole bestie lineup, fr fr:


That's the whole page, bestie 🫢 This overlay_get_target_phandle(9) page came from source/version ./scripts/dtc/libfdt and is dated October 2026 β€” periodt. πŸ’‹

πŸ“¦ where this page comes from