STRUCT HOST1X_BO_OPS(9)
π struct host1x_bo_ops(9) π
okay so welcome to the Kernel API Manual bestie, today we're talking about struct host1x_bo_ops and honestly? she's giving backstage-pass energy. π
β¨ NAME β¨
struct host1x_bo_ops β literally the operations implemented by a host1x_bo provider. that's the whole vibe. that's her job. π¦
πΈ SYNOPSIS πΈ
struct host1x_bo_ops {
struct host1x_bo *(*get)(struct host1x_bo *bo);
void (*put)(struct host1x_bo *bo);
struct host1x_bo_mapping *(*pin)(struct device *dev, struct host1x_bo *bo, enum dma_data_direction dir);
void (*unpin)(struct host1x_bo_mapping *map);
void *(*mmap)(struct host1x_bo *bo);
void (*munmap)(struct host1x_bo *bo, void *addr);
};
six function pointers, one struct, zero notes. she's a whole squad of callbacks and she ate. π₯
π Members π
okay so not every member got her lil bio written out here β the docs are lowkey selective, ngl β but the two that did get one? absolute icons. π
pinβ create a DMA mapping. and hear me LOUD: the implementation must not touch the bo'srefcount. like, do not. hands off. not yours. πunpinβ destroy a DMA mapping. same rule, bestie: the implementation must not touch the bo'srefcount. periodt. π
fr fr, that refcount warning shows up twice because it's that serious. implementation says no touching. π«Ά
π SEE ALSO π
- the kernel file
./include/linux/host1x.hβ go read it, it's right there struct host1x_bo_cache(9)struct host1x_client_ops(9)struct host1x_client(9)struct host1x_driver(9)
the whole host1x friend group honestly, they all show up together ππ
π¦ and that's the page! sourced from the kernel path ./include/linux, dated October 2026, all about struct host1x_bo_ops(9) β go forth and map those DMA buffers responsibly, mwah πβ¨
π¦ 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