afu_mmio_re...et_by_offset(9)
π 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 β
0on success π- a negative error code otherwise π (not me getting a negative backβ¦)
π¦ SEE ALSO π¦
- Kernel file
./drivers/fpga/dfl-afu-region.c afu_mmio_region_init(9)afu_mmio_region_add(9)afu_mmio_region_destroy(9)afu_mmio_region_get_by_index(9)
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
- 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