fw_devlink_refresh_fwnode(9)

📦 version 7.3.1, in nixpkgs unstable

okay so bestie, this one's from the Kernel API Manual (section 9, kernel-adjacent, very much "the adults are talking" energy) and it's honestly so niche but so iconic. It's literally one function, one argument, and then a SEE ALSO list that goes on for communities. Buckle up 🎀

✨ NAME ✨

fw_devlink_refresh_fwnode — recheck the tree under this firmware node 🌳

Like, the whole job. Recheck the tree. Under this fwnode. That's the vibe check right there.

🌸 SYNOPSIS 🌸

void fw_devlink_refresh_fwnode (struct fwnode_handle *fwnode );

Returns nothing (void), takes one pointer, doesn't miss. Periodt. ✨

🦋 ARGUMENTS 🦋

  • fwnode — the fwnode under which the fwnode tree has changed. That's it, that's the tea 💅 It's the node whose little subtree went through a glow-up (or a whole restructuring, no shade), and this is the node you point at.

💖 DESCRIPTION 💖

So here's the situation. This function is mainly meant to adjust the supplier/consumer dependencies after a fwnode tree overlay has occurred.

Read that again, bestie: something in the tree got overlaid — moved, added, rearranged — and now the supplier/consumer relationships are lowkey out of sync with reality. This function is the one that goes "okay, let's recheck everything under this node and get the dependencies matching the tree again." 🔥

Not me caring deeply about dependency graphs. It's giving main character energy honestly. 😭

It's mainly for that overlay case — that's the framing the doc gives, so that's what we're saying. No inventing extra behaviour, I would never 🙈

🔥 SEE ALSO 🔥

okay this is the part where I need you to sit down. This list is long. Like, "texting the group chat at 3am" long. But every single one of them is a real reference and I'm not skipping a single one, because we don't do that here 👑

First, the source: this all lives in the kernel file ./drivers/base/core.c 🫶

The fwnode link crew:

Dependency + PM squad:

Tree-walking & cycle-relaxing:

Device core, the whole entire life:

Iterate the children, iconically:

Offline/online & root devices:

Create/destroy/rename/move the whole device:

Probe-y bits:

Fwnode↔device glue (the actual besties):

That's the whole list, all 76 references, not one dropped, because I love you and I respect the documentation 💜

lowkey sign-off: this page lives in ./drivers/base, and it's dated October 2026 in the fw_devlink_refresh_fwnode(9) manual. Go recheck your trees, bestie, and hydrate while you're at it 🍓🧚💜

📦 where this page comes from