fwnode_get_phy_mode(9)

💖 fwnode_get_phy_mode(9) — the Kernel API Manual, bestie edition 🎀

okay so real talk: this is a page from the Kernel API Manual, and it's about fwnode_get_phy_mode(9). Yes that's a mouthful, no we're not changing it, it's iconic. Let's get into it ✨

---

🌸 NAME 🌸

fwnode_get_phy_mode — bestie, it literally gets the phy mode for the given firmware node. That's the whole personality. 💅

---

✨ SYNOPSIS ✨

int fwnode_get_phy_mode (const struct fwnode_handle *fwnode );

that's it. that's the vibe. one function, one pointer, one int coming back at you 🫶

---

🦋 ARGUMENTS 🦋

• fwnode — pointer to the given node, fr fr. that's the one you're handing over. no cap, that's all it wants.

---

💜 DESCRIPTION 💜

okay so here's what it does: the function pulls the phy interface string out of the property 'phy-mode' — or, plot twist, it hits an error case. 😭 that's the tealeaves, that's the whole story.

so like — property 'phy-mode', string in, error case as the alternative. main character energy for a single property lookup, honestly. 👑

---

🌈 SEE ALSO 🌈

buckle up bestie, this list is long and every single one of them ate. first up, the kernel file:

Kernel file ./drivers/base/property.c

and the iconics:

• device_property_present(9)
• fwnode_property_present(9)
• device_property_read_bool(9)
• fwnode_property_read_bool(9)
• device_property_read_u8_array(9)
• device_property_read_u16_array(9)
• device_property_read_u32_array(9)
• device_property_read_u64_array(9)
• device_property_read_string_array(9)
• device_property_read_string(9)
• device_property_match_string(9)
• fwnode_property_read_u8_array(9)
• fwnode_property_read_u16_array(9)
• fwnode_property_read_u32_array(9)
• fwnode_property_read_u64_array(9)
• fwnode_property_read_string_array(9)
• fwnode_property_read_string(9)
• fwnode_property_match_string(9)
• fwnode_property_match_property_string(9)
• fwnode_property_get_reference_args(9)
• fwnode_find_reference(9)
• fwnode_get_name(9)
• fwnode_get_name_prefix(9)
• fwnode_name_eq(9)
• fwnode_get_parent(9)
• fwnode_get_next_parent(9)
• fwnode_count_parents(9)
• fwnode_get_nth_parent(9)
• fwnode_get_next_child_node(9)
• fwnode_get_next_available_child_node(9)
• device_get_next_child_node(9)
• fwnode_get_named_child_node(9)
• device_get_named_child_node(9)
• fwnode_handle_get(9)
• fwnode_device_is_available(9)
• fwnode_get_child_node_count(9)
• fwnode_get_named_child_node_count(9)
• device_get_phy_mode(9)
• fwnode_iomap(9)
• fwnode_irq_get(9)
• fwnode_irq_get_byname(9)
• fwnode_graph_get_next_endpoint(9)
• fwnode_graph_get_port_parent(9)
• fwnode_graph_get_remote_port_parent(9)
• fwnode_graph_get_remote_port(9)
• fwnode_graph_get_remote_endpoint(9)
• fwnode_graph_get_endpoint_by_id(9)
• fwnode_graph_get_endpoint_count(9)
• fwnode_graph_parse_endpoint(9)
• fwnode_connection_find_match(9)
• fwnode_connection_find_matches(9)

like I said. every. single. one. 🌈💀 and yes you should go read them, iykyk.

---

🎀 sign-off 🎀

this lil masterpiece comes to you from the source ./drivers/base, dated October 2026, and it's filed under fwnode_get_phy_mode(9) in the Kernel API Manual. slay, go read your firmware nodes, mwah 💋💖✨