fpga_bridge_get(9)

✨ fpga_bridge_get ✨

Okay bestie, welcome to the fpga_bridge_get page from the Kernel API Manual, section 9 🫶 this one's short and sweet but she's important, so pay attention.

🌸 NAME 🌸

fpga_bridge_get — get an exclusive reference to an fpga bridge 👑

🎀 SYNOPSIS 🎀

struct fpga_bridge * fpga_bridge_get (struct device *dev , struct fpga_image_info *info );

🦋 ARGUMENTS 🦋

• dev — the parent device that the fpga bridge was registered with 🧚 this is your starting point, the one you already know about.
• info — the fpga image specific information 💖 the deets about the image, basically.

💅 DESCRIPTION 💅

So here's the vibe: you hand it a device, and it hands you back an exclusive reference to an fpga bridge. That's it. That's the whole thing. Literally giving you the keys 🔑 and nobody else gets to hold them while you've got them.

⭐ RETURN ⭐

You get back the fpga bridge struct — or, if things go sideways, an IS_ERR condition containing an error code 😭 so like, always check, okay? Don't be out here dereferencing without a vibe check.

🌈 SEE ALSO 🌈

• Kernel file ./drivers/fpga/fpga-bridge.c — that's where the magic lives, iykyk
• fpga_bridge_enable(9)
• fpga_bridge_disable(9)
• of_fpga_bridge_get(9)
• fpga_bridge_put(9)
• fpga_bridges_enable(9)
• fpga_bridges_disable(9)
• fpga_bridges_put(9)
• of_fpga_bridge_get_to_list(9)
• fpga_bridge_get_to_list(9)
• __fpga_bridge_register(9)
• fpga_bridge_unregister(9)

And that's the whole page, bestie — go forth and bridge 🫶🦋

Cute little sign-off: this one lives in ./drivers/fpga, dated October 2026, and it's the fpga_bridge_get(9) page you just read 💜 periodt.