acpi_graph_g...ote_endpoint(9)

💅 NAME

Okay bestie, gather round, because this is acpi_graph_get_remote_endpoint — and yes, it parses and returns the remote end of an endpoint. That's the whole vibe. It's from the Kernel API Manual, and it's lowkey iconic for doing exactly one job and doing it slayfully. ✨

---

🌸 SYNOPSIS

struct fwnode_handle * acpi_graph_get_remote_endpoint (const struct fwnode_handle *__fwnode );

Like, that's the whole signature. No cap. 🫶

---

🎀 ARGUMENTS

• __fwnode — the endpoint firmware node pointing to a remote device. Think of it as the little node that says "hey, my remote bestie is over there" 💫

---

🦋 DESCRIPTION

Returns the remote endpoint corresponding to __fwnode. And if something goes wrong? NULL on error. That's it. That's the function. Fr fr. 😭💖

No extra lore, no side quests — just remote endpoint in, remote endpoint out. Periodt. 💅

---

🔥 SEE ALSO

Kernel file ./drivers/acpi/property.c — and the whole friend group:

• acpi_data_get_property(9)
• acpi_dev_get_property(9)
• acpi_node_prop_get(9)
• acpi_data_get_property_array(9)
• __acpi_node_get_property_reference(9)
• acpi_node_prop_read(9)
• acpi_node_get_parent(9)
• acpi_graph_get_next_endpoint(9)
• acpi_graph_get_child_prop_value(9)

---

So anyway, this little page lives in ./drivers/acpi, dated October 2026, and it's giving "kernel API but make it cute" energy. Go off, bestie. 🌈👑