set_primary_fwnode(9)

✨ set_primary_fwnode(9) ✨

okay so this is a page from the Kernel API Manual, and bestie, it's a short one but it's lowkey important — it's all about who gets to be the main character firmware node of a device 💅

---

🌸 NAME 🌸

set_primary_fwnode — Change the primary firmware node of a given device.

Like, you're literally swapping out the headliner. No cap.

---

🎀 SYNOPSIS 🎀

void set_primary_fwnode (struct device *dev , struct fwnode_handle
*fwnode );

It returns void, so don't go looking for a return value, there isn't one, periodt.

---

💖 ARGUMENTS 💖

• dev — Device to handle. This is the one getting a whole new primary firmware node, she's the main character here.
• fwnode — New primary firmware node of the device. The fresh face taking the top spot.

---

🦋 DESCRIPTION 🦋

Set the device's firmware node pointer to fwnode, but if a secondary firmware node of the device is present, preserve it. 🫶

Translation: fwnode becomes the primary, but if there's already a secondary hanging around, she stays — nobody's getting evicted today bestie.

Valid fwnode cases are:

• primary --> secondary --> -ENODEV
• primary --> NULL
• secondary --> -ENODEV
• NULL

Those are the only vibes that pass the vibe check, iykyk. Everything else? Not on the list 🙈

---

🌈 SEE ALSO 🌈

The whole friend group, fr fr — like genuinely a lot of them, and yes we're listing every single one because leaving people out is rude 💀

• __fwnode_link_add(9)
• __fwnode_link_del(9)
• __fwnode_link_cycle(9)
• fwnode_links_purge_suppliers(9)
• fwnode_links_purge_consumers(9)
• fwnode_links_purge(9)
• __fwnode_links_move_consumers(9)
• __fw_devlink_pickup_dangling_consumers(9)
• fw_devlink_refresh_fwnode(9)
• device_is_dependent(9)
• device_pm_move_to_tail(9)
• device_link_wait_removal(9)
• device_link_add(9)
• device_link_del(9)
• device_link_remove(9)
• device_links_check_suppliers(9)
• __device_links_queue_sync_state(9)
• device_links_flush_sync_list(9)
• device_links_force_bind(9)
• device_links_driver_bound(9)
• __device_links_no_driver(9)
• device_links_no_driver(9)
• device_links_driver_cleanup(9)
• device_links_busy(9)
• device_links_unbind_consumers(9)
• device_links_purge(9)
• wait_for_init_devices_probe(9)
• fwnode_is_ancestor_of(9)
• fwnode_get_next_parent_dev(9)
• __fw_devlink_relax_cycles(9)
• fw_devlink_create_devlink(9)
• __fw_devlink_link_to_consumers(9)
• __fw_devlink_link_to_suppliers(9)
• dev_driver_string(9)
• device_release(9)
• devm_device_add_group(9)
• devices_kset_move_before(9)
• devices_kset_move_after(9)
• devices_kset_move_last(9)
• device_create_file(9)
• device_remove_file(9)
• device_remove_file_self(9)
• device_create_bin_file(9)
• device_remove_bin_file(9)
• device_initialize(9)
• kobject_has_children(9)
• dev_set_name(9)
• device_add(9)
• device_register(9)
• get_device(9)
• put_device(9)
• device_del(9)
• device_unregister(9)
• device_get_devnode(9)
• device_for_each_child(9)
• device_for_each_child_reverse(9)
• device_for_each_child_reverse_from(9)
• device_find_child(9)
• device_offline(9)
• device_online(9)
• __root_device_register(9)
• root_device_unregister(9)
• device_create(9)
• device_create_with_groups(9)
• device_destroy(9)
• device_rename(9)
• device_move(9)
• device_change_owner(9)
• device_shutdown(9)
• dev_err_probe(9)
• dev_warn_probe(9)
• set_secondary_fwnode(9)
• device_remove_of_node(9)
• device_add_of_node(9)
• device_set_of_node_from_dev(9)
• get_dev_from_fwnode(9)

ngl if you read all 76 of those you're iconic and also maybe touch some grass 🌱 but ily for it

---

👑 the cute sign-off 👑

This one lives in ./drivers/base, it's dated October 2026, and it's from the pages of that Kernel API Manual we mentioned at the top 💜 That's the whole page bestie — stay slay, read your manpages, and may your firmware node always be primary ✨🎀