acpi_graph_...d_prop_value(9)

💅 acpi_graph_get_child_prop_value(9) — the group-chat edition

okay so bestie, welcome to the kernel API manual for acpi_graph_get_child_prop_value — yes that's the whole name, the header up top literally abbreviates it to acpi_graph_...d_prop_value(9) because it's that long, iconic behaviour honestly 🎀

---

✨ NAME ✨

acpi_graph_get_child_prop_value — return a child with a given property value 🌸

Like, you give it a property, you give it a value, it finds you the child that matches. matchmaking but for firmware nodes, we love to see it 💖

---

✨ SYNOPSIS ✨

struct fwnode_handle * acpi_graph_get_child_prop_value (const struct fwnode_handle *fwnode , const char *prop_name , unsigned int val );

three args, one pointer back, slay ✨

---

✨ ARGUMENTS ✨

• fwnode — device fwnode 🦋 like, the node you're starting from, your main character
• prop_name — the name of the property to look for 🔍 the thing we're checking
• val — the desired property value ⭐ the vibe we want it to match

---

✨ DESCRIPTION ✨

so what it actually does: it returns the port node that corresponds to a given port number 💅

and the returns are giving very clear-cut:

• child node on success 👑
• NULL otherwise 💀

no in-between, no "it depends", periodt.

---

✨ SEE ALSO ✨

go read the kernel file ./drivers/acpi/property.c bestie, it's right there 🙈 and while you're in the neighbourhood, these are all friends of the family:

• 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_remote_endpoint(9)

that's the whole little friend group, iykyk 🌈

---

aaand that's the page!! courtesy of ./drivers/acpi, dated October 2026, still serving the same acpi_graph_...d_prop_value(9) realness as always 💜🫶 go forth and get your child prop values bestie, mwah 🎀