platform_device_set_fwnode(9)

📦 version 7.3.1, in nixpkgs unstable

💅 platform_device_set_fwnode(9)

okay so bestie, welcome to the Kernel API Manual — yes that's the manual name, no it's not a vibe, it's a whole reference library and we're living in it now 🫶

✨ NAME ✨

platform_device_set_fwnode — the function that assigns a firmware node to a device, and honestly? it's giving matchmaker energy 🔥

🌸 SYNOPSIS 🌸

void platform_device_set_fwnode (struct platform_device *pdev , struct
       fwnode_handle *fwnode );

like, look at that signature. void return, so it hands you nothing back — it just does the thing and dips 💅

🎀 ARGUMENTS 🎀

  • pdev — the platform device you're setting the node for. yeah. that one. your fave platform device 💖
  • fwnode — the new firmware node you're blessing it with ✨

🦋 DESCRIPTION 🦋

okay so the whole point: you assign a firmware node to this platform device. that's it, that's the plot 🎬

but here's the tea — internally it keeps track of the reference count for you. like a responsible bestie who remembers who owes whom 🧾

⚠️ big one: devices created with platform_device_alloc must use this function instead of assigning the node manually. no DIY shortcuts, no "I'll just do it myself real quick", none of that. use the function. periodt 👑
💀 also very serious: this function must not be called for a platform device that already has a software node as its primary firmware node assigned. like, don't. it's not a vibe. that's the one rule and we respect it 🙈

🌈 SEE ALSO 🌈

Kernel file ./drivers/base/platform.c — the source file, the mothership 🚀 and its whole friend group:

that's the whole page, bestie, you ate it 💅✨ signing off from ./drivers/base — dated October 2026 — version platform_device_set_fwnode(9), no cap 🫶🎀

📦 where this page comes from