of_fpga_bridge_get_to_list(9)
π of_fpga_bridge_get_to_list(9) π
okay so bestie, welcome to the Kernel API Manual β¨ this one's a little function with a big job and honestly? she ate. let's get into it π«Ά
πΈ NAME πΈ
of_fpga_bridge_get_to_list β grab yourself a bridge and yeet it onto a list, no cap π
β¨ SYNOPSIS β¨
int of_fpga_bridge_get_to_list (struct device_node *np , struct
fpga_image_info *info , struct list_head *bridge_list );
π ARGUMENTS π
npβ the node pointer of an FPGA bridge, like her little name tag π·οΈinfoβ the fpga image specific information, aka the lore she needs πΈbridge_listβ list of FPGA bridges, the group chat she's about to join π¬
π¦ DESCRIPTION π¦
okay so what she does is: get an exclusive reference to the bridge, and then put it on the list. that's it, that's the whole vibe π β¨ exclusive reference means she's claimed, bestie, main character energy only π
π RETURN π
0for success π slay- otherwise you get the error code from
of_fpga_bridge_getπ so like, if it's not zero, something went sideways and it's giving struggle
π SEE ALSO π
Kernel file ./drivers/fpga/fpga-bridge.c and honestly the whole bridge crew, they all link up π«Ά:
fpga_bridge_enable(9)fpga_bridge_disable(9)of_fpga_bridge_get(9)fpga_bridge_get(9)fpga_bridge_put(9)fpga_bridges_enable(9)fpga_bridges_disable(9)fpga_bridges_put(9)fpga_bridge_get_to_list(9)__fpga_bridge_register(9)fpga_bridge_unregister(9)
ngl bestie, fpga_bridge_get_to_list(9) is right there in SEE ALSO too β she's literally referencing herself, iconic behavior, iykyk πβ¨
and that's the whole page!! mwah π this came from ./drivers/fpga and it's dated October 2026 β go forth and get those bridges onto those lists, fr fr πππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms