STRUCT OMAP_IOMMU_ARCH_DATA(9)
π struct omap_iommu_arch_data(9) π
okay so bestie, welcome to the Kernel API Manual page for struct omap_iommu_arch_data β yes it's a mouthful, no you don't have to say it out loud. let's get into it β¨
π NAME π
struct omap_iommu_arch_data β the omap iommu private data. literally what it says on the tin, no cap.
π¦ SYNOPSIS π¦
here's the whole entire struct, and honestly? it's giving minimalism icon:
struct omap_iommu_arch_data {
struct omap_iommu *iommu_dev;
};
πΈ Members πΈ
iommu_devβ the handle of the OMAP iommu device. that's it, that's the only member, and she ate π
β¨ Description β¨
okay so picture this: this is an omap iommu private data object, and what it does is bind an iommu user to its iommu device. matching them up. making it official π«Ά
and here's the part that matters, bestie: this object should be placed at the iommu user's dev_archdata β so that the generic IOMMU API can be used without having to utilize omap-specific plumbing anymore. yes. no more omap-specific plumbing. we love a glow-up that deletes code. π₯
π SEE ALSO π
- Kernel file
./drivers/iommu/omap-iommu.h struct omap_iommu_device(9)struct omap_iommu_domain(9)
and that's the whole vibe check π this little love letter to the kernel lives over in ./drivers/iommu, dated October 2026, and it's struct omap_iommu_arch_data(9) forever and always. mwah π stay slay, stay mapped π§
π¦ 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