dfl_fme_create_region(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ dfl_fme_create_region(9) ✨

okay so bestie, welcome to the Kernel API Manual πŸ’– this one's called dfl_fme_create_region and it lives in the kernel, section 9. it's giving "glow-up for a platform device" energy, iykyk πŸ¦‹


🌸 NAME 🌸

dfl_fme_create_region β€” literally creates an fpga region platform device as a child πŸŽ€

like. that's the whole vibe. it makes the region device, and that device is a child. no cap.


✨ SYNOPSIS ✨

struct dfl_fme_region * dfl_fme_create_region (struct
dfl_feature_dev_data *fdata , struct platform_device *mgr , struct
platform_device *br , int port_id );

she takes four things and hands you back a pointer. slay πŸ”₯


🫢 ARGUMENTS 🫢

  • fdata β€” the fme feature dev data πŸ’… that's the feature dev data for the fme, bestie, it's right there in the name.
  • mgr β€” the mgr platform device, which is needed for the region πŸ‘‘
  • br β€” the br platform device, also needed for the region 🌈
  • port_id β€” the port id πŸ“ (yes. that's it. that's the description. iconic of the original honestly)

⭐ RETURN ⭐

you get the fme region if it worked, and an error code otherwise 😭 so like. always check. don't just trust it. fr fr.


πŸ¦‹ SEE ALSO πŸ¦‹

kernel file ./drivers/fpga/dfl-fme-pr.c β€” go read it, it's right there πŸ’œ

and the whole friend group:

notice how there's a create and a destroy for basically everything? yeah. that's the circle of life, kernel edition πŸ’€ please actually call the destroy ones, i'm begging πŸ™ˆ


lowkey a reminder: this page is from ./drivers/fpga and it's dated October 2026 β€” that's the source/version and date info, bestie, don't come for me, it's in the footer of the original and now it's in this cute little sign-off instead πŸŽ€

okay that's the whole page, mwah, go forth and create regions responsibly πŸ’–βœ¨πŸ§š

πŸ“¦ where this page comes from