STRUCT OMAP_IOMMU_DOMAIN(9)
π struct omap_iommu_domain(9) π
okay so bestie, welcome to the Kernel API Manual β¨ β today's main character is struct omap_iommu_domain, which is literally, as the name suggests, an omap iommu domain π. that's it. that's the vibe.
πΈ NAME πΈ
struct omap_iommu_domain β omap iommu domain π¦
β¨ SYNOPSIS β¨
here's the whole glow-up, copied exactly, no cap:
struct omap_iommu_domain {
u32 num_iommus;
struct omap_iommu_device *iommus;
struct device *dev;
spinlock_t lock;
struct iommu_domain domain;
};
π Members π
num_iommusβ the count of iommus chilling in this domain. literally just a number,u32coded πiommusβ the omap iommu device data for all the iommus in this domain. everyone's invited to the party π«Άdevβ thestruct devicethat's using this domain. the one actually living here πlockβ the domainspinlock_t, and bestie listen: you should take it when attaching/detaching. not optional, not a suggestion, fr fr πdomainβ the generic domain handle that the iommu core code uses. it's giving "behind the scenes manager" energy π
π¦ SEE ALSO π¦
- Kernel file
./drivers/iommu/omap-iommu.hβ go read it, iykyk π struct omap_iommu_device(9)struct omap_iommu_arch_data(9)
and that's the whole page, bestie π
cute lil sign-off: this icon was brought to you by the source./drivers/iommu, dated October 2026, footer versionstruct omap_iommu_domain(9)πβ¨π
π¦ 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