tb_ring_dma_device(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– tb_ring_dma_device(9) πŸ’–

okay bestie, welcome to the tb_ring_dma_device(9) page from the Kernel API Manual β€” this one is short, sweet, and lowkey iconic ✨


🌸 NAME 🌸

tb_ring_dma_device β€” Return device used for DMA mapping 🫢


✨ SYNOPSIS ✨

struct device * tb_ring_dma_device (struct tb_ring *ring );

that's the whole signature, no cap πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • ring β€” Ring whose DMA device is retrieved. yep, that's the ring you're asking about πŸ’–

πŸ¦‹ DESCRIPTION πŸ¦‹

Here's the vibe: use this function when you are mapping DMA for buffers that are passed to the ring for sending/receiving. that's literally its moment to shine ⭐


πŸ”₯ RETURN πŸ”₯

Pointer to device used for DMA mapping. that's the whole return, bestie πŸ‘‘


🌈 SEE ALSO 🌈

Kernel file ./include/linux/thunderbolt.h, plus enum tb_security_level(9), struct tb(9), struct tb_property_dir(9), struct tb_property(9), enum tb_link_width(9), struct tb_xdomain(9), struct tb_protocol_handler(9), struct tb_service(9), struct tb_service_driver(9), struct tb_nhi(9), struct tb_ring(9), enum ring_desc_flags(9), struct ring_frame(9), tb_ring_rx(9), and tb_ring_tx(9) 🧚


made with πŸ’œ from the ./include/linux source, dated October 2026 β€” catch you on the tb_ring_dma_device(9) page, bestie πŸ«ΆπŸŽ€

πŸ“¦ where this page comes from