afu_mmio_re...et_by_offset(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… afu_mmio_region_get_by_offset β€” Kernel API Manual ✨

okay so bestie, we're in the <pink>kernel API manual</pink> today and the star of the show is afu_mmio_region_get_by_offset(9) πŸŽ€ β€” that's the section 9 girlies, kernel functions only, no cap.


🌸 NAME 🌸

afu_mmio_region_get_by_offset β€” literally finds an afu mmio region by <italic>offset</italic> and <italic>size</italic> πŸ¦‹


✨ SYNOPSIS ✨

int afu_mmio_region_get_by_offset (struct dfl_feature_dev_data *fdata ,
u64 offset , u64 size , struct dfl_afu_mmio_region *pregion );

πŸŽ€ ARGUMENTS πŸŽ€

  • fdata β€” the afu feature dev data. yes it's that girl πŸ’–
  • offset β€” the region offset, measured from the start of the device fd. counting from the top, periodt πŸ“
  • size β€” the region size. how much region we're talking about 🌈
  • pregion β€” a ptr to the region for the result. that's where the answer goes, bestie 🫢

πŸ’œ DESCRIPTION πŸ’œ

Okay so here's the vibe: it finds the region that fully contains the region described by the input parameters (offset and size) β€” and it goes looking for it in the feature dev's region linked list πŸ”₯

like… fully contains. not "kind of overlaps," not "is adjacent to." fully. vibe check passed only if the whole thing fits inside. πŸ‘‘


⭐ RETURN ⭐

  • 0 on success πŸŽ‰
  • a negative error code otherwise 😭 (not me getting a negative back…)

πŸ¦‹ SEE ALSO πŸ¦‹


ngl, go read dfl-afu-region.c if you want the full lore β€” the whole friend group lives in there πŸ’€

and that's the page!! mwah πŸ’‹ this one's brought to you by the <purple>./drivers/fpga</purple> girlies, dated <cyan>October 2026</cyan> β€” <rainbow>afu_mmio_region_get_by_offset(9)</rainbow> out, slay, see you in the next manpage πŸ§šβ€β™€οΈπŸ’…πŸŒΈ

πŸ“¦ where this page comes from