arm_iommu_map_phys(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– arm_iommu_map_phys(9) πŸ’–

okay so bestie, welcome to the Kernel API Manual ✨ β€” this is arm_iommu_map_phys(9), and no, the NAME section lowkey has no description, that's just how it ships, we don't ask questions 🫢


🌸 NAME 🌸

arm_iommu_map_phys β€” and that's literally it, the description slot is empty, the void, nothing there, so don't come for me 😭 (the manual genuinely leaves it blank, fr fr)


✨ SYNOPSIS ✨

dma_addr_t arm_iommu_map_phys (struct device *dev , phys_addr_t phys ,
       size_t size , enum dma_data_direction dir , unsigned long attrs );

so it hands you back a dma_addr_t, that's the vibe πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • dev β€” a valid struct device pointer πŸ‘‘ and yes valid is doing a LOT of heavy lifting in that sentence, please respect it
  • phys β€” the physical address that the buffer resides in πŸ“ that's its whole home address
  • size β€” size of the buffer to map, like how much of it we're claiming 🌸
  • dir β€” the DMA transfer direction, iykyk πŸ¦‹
  • attrs β€” the DMA mapping attributes ✨ lil extra seasoning

πŸ’€ DESCRIPTION πŸ’€

it's the IOMMU aware version of arm_dma_map_page 🧚 that's the entire description, she's concise, she's iconic, she said what she said periodt πŸ”₯


🌈 SEE ALSO 🌈

like, the whole friend group, they roll together 🫢


ngl bestie this one's a shortie β€” but every single one of those eight SEE ALSO pages is listed up there, no cap, I didn't skip a single one πŸ™ˆ

and that's the page!! πŸ“ this little gem lives in ./arch/arm/mm and the date on it is October 2026, so mark your calendar ⭐ mwah, go map some physical memory for your device, slay πŸ’œ

πŸ“¦ where this page comes from