__fwnode_li...ve_consumers(9)

💅 __fwnode_li...ve_consumers(9) — a Kernel API Manual moment ✨

okay so welcome to the Kernel API Manual, bestie. this one's a (9) page, which is kernel-API territory, and it's literally about shuffling consumers around between fwnodes. tiny function, big group-chat energy. let's go 🫶

---

🌸 NAME 🌸

__fwnode_links_move_consumers — move consumer from from to to fwnode_handle

like, that's the whole vibe. one job. it does the job. iconic.

---

✨ SYNOPSIS ✨

void __fwnode_links_move_consumers (struct fwnode_handle *from , struct
fwnode_handle *to );

no return value, no drama, void all the way. we love a function that doesn't hand you a status code to overthink 💀

---

🎀 ARGUMENTS 🎀

• from — move consumers away from this fwnode. she's the one being vacated, no cap.
• to — move consumers to this fwnode. she's the new home, main character energy 👑

---

🦋 DESCRIPTION 🦋

Move all consumer links from from fwnode to to fwnode.

that's it. that's the whole description. every single consumer link that was chilling on from gets relocated over to to. not some of them, not the cute ones — all of them. periodt 💅

---

🌈 SEE ALSO 🌈

the kernel file lives at ./drivers/base/core.c and honestly the friend group here is huge. buckle up, bestie, we're doing the whole roster 🍓

• __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)
• __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_primary_fwnode(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)

like… that's a whole friend group 😭 every one of them is a (9) and every one of them is invited to the function.

---

lowkey a reminder bestie: this page is __fwnode_li...ve_consumers(9) from Kernel API Manual, it lives under ./drivers/base, and it's dated October 2026. go read the actual source before you @ me 🙈

stay slay, keep your fwnodes tidy, and may all your consumers land exactly where you moved them 💖🧚‍♀️✨