iort_get_iort_node(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 iort_get_iort_node πŸ’…

okay bestie, welcome to the Kernel API Manual β€” yes that's the whole vibe, we're reading kernel docs together and honestly? iconic. this page is about iort_get_iort_node, and it does exactly one little job, but it does it slayfully πŸŽ€


✨ NAME ✨

iort_get_iort_node β€” the function that goes and retrieves the iort_node associated with an fwnode πŸ¦‹

like, you hand it a firmware node and it hands you back the IORT node that's linked to it. match made in heaven, no cap.


🌈 SYNOPSIS 🌈

struct acpi_iort_node * iort_get_iort_node (struct fwnode_handle *fwnode
);

that return type is struct acpi_iort_node * btw β€” pointer, pointer energy πŸ‘‘


πŸ’– ARGUMENTS πŸ’–

  • fwnode β€” the fwnode associated with the device that you wanna look up 🫢 literally just pass in the firmware node of the device you're curious about, and the lookup happens from there.

⭐ RETURN ⭐

on success you get an iort_node pointer back πŸ’«

on failure? NULL. that's it. no drama, just NULL, so pls remember to check it before you dereference, bestie πŸ˜­πŸ’€


πŸ”₯ SEE ALSO πŸ”₯

the kernel file lives at ./drivers/acpi/arm64/iort.c β€” that's the whole source of truth for this one, go read it if you're feeling main character energy πŸ“–βœ¨

and here's the whole friend group of sibling functions, all of them (9) manpages, all of them relevant:

like, that's the entire group chat right there β€” all of them in ./drivers/acpi/arm64, all of them (9), all of them waiting for you to read them 🌸


lowkey reminder: the source path for the whole crew is ./drivers/acpi/arm64 and this page is dated October 2026 β€” yes, future girlie vibes β³πŸ’…

kk that's the page, go forth and retrieve those iort_nodes responsibly, mwah πŸ’œπŸ§š

πŸ“¦ where this page comes from