ntb_get_dma_dev(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ntb_get_dma_dev(9) β€” the Kernel API Manual glow-up

okay so bestie, welcome to ntb_get_dma_dev(9), straight out of the Kernel API Manual ✨ this one's short, sweet, and honestly kinda iconic for how much it just handles for you.


🌸 NAME 🌸

ntb_get_dma_dev β€” grab the device you should be using for DMA allocations/mappings πŸ’–


✨ SYNOPSIS ✨

struct device * ntb_get_dma_dev (struct ntb_dev *ntb );

like, that's the whole signature. so clean. so demure. πŸŽ€


🫢 ARGUMENTS 🫢

  • ntb β€” the NTB device context. that's your main character right there πŸ‘‘

πŸ’… DESCRIPTION πŸ’…

so this returns a struct device that's suitable for DMA API allocations and mappings. ngl that's the whole vibe ✨

most of the time it's just the parent of the NTB device β€” like, the obvious answer, no drama β€” but a driver can override it by implementing .get_dma_dev. lowkey customisation, highkey useful πŸ¦‹

⚠️ real talk though: drivers that implement .get_dma_dev must return a non-NULL pointer. no NULLs. not the move. not today. periodt πŸ’€

⭐ RETURN ⭐

a device pointer to use for DMA operations 🫑 go forth and allocate, bestie.


🌈 SEE ALSO 🌈

sooo everything lives in the kernel file ./include/linux/ntb.h, and honestly the whole NTB extended universe shows up here. it's giving family reunion πŸŽ‰

like… yes. all of them. every single one. iykyk 🧚


okay that's the whole page bestie 🫢 this cutie lives in ./include/linux, dated October 2026, and it answers to the name ntb_get_dma_dev(9). go get your DMA on. slay. πŸ’œ

πŸ“¦ where this page comes from