ttm_kmap_ite...near_io_init(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

ttm_kmap_iter_linear_io_init β€” bestie, this one initializes an iterator for linear io memory ✨

(also hi, you're reading the Kernel API Manual, welcome to the group chat 🫢)


🌸 SYNOPSIS 🌸

struct ttm_kmap_iter * ttm_kmap_iter_linear_io_init (struct
ttm_kmap_iter_linear_io *iter_io , struct ttm_device *bdev , struct
ttm_resource *mem );

πŸŽ€ ARGUMENTS πŸŽ€

  • iter_io β€” the iterator you're initializing. it's the main character here πŸ’…
  • bdev β€” the TTM device. your devicey device, ngl πŸ¦‹
  • mem β€” the ttm resource that represents the iomap πŸ‘‘

✨ DESCRIPTION ✨

okay so real talk: this function is for internal TTM use only πŸ™ˆ like, if you're not TTM, this is not your moment, bestie.

what it does is set up a memcpy kmap iterator pointing at a linear chunk of io memory. that's it, that's the vibe. lowkey iconic, highkey specific πŸ’–


πŸ”₯ RETURN πŸ”₯

you get back a pointer to the embedded struct ttm_kmap_iter β€” or an error pointer on failure 😭 (so like… vibe check your return value, fr fr)


πŸ¦‹ SEE ALSO πŸ¦‹

the kernel file lives at ./drivers/gpu/drm/ttm/ttm_resource.c β€” go say hi, it's literally right there 🧚

and the whole friend group:


and that's a wrap, bestie πŸŒˆπŸ’œ

this page came from ./drivers/gpu/drm/ttm, dated October 2026, and it goes by ttm_kmap_ite...near_io_init(9) (yes the title got truncated, no it's not a typo, the manual really said that πŸ’€). periodt. πŸŽ€

πŸ“¦ where this page comes from