knav_pool_desc_map(9)

💫 NAME 💫

knav_pool_desc_map — the glow-up where a descriptor gets mapped for DMA transfer ✨

ok so real talk, this is the function in the Kernel API Manual (that's the manual name, bestie, we're in section 9) that takes your descriptor and maps it for DMA. it's giving "matchmaker but for memory" 💅

---

🌸 SYNOPSIS 🌸

int knav_pool_desc_map (void *ph , void *desc , unsigned size ,
       dma_addr_t *dma , unsigned *dma_sz );

like, look at her. five args, returns an int, no cap 🫶

---

🎀 ARGUMENTS 🎀

• ph — the pool handle 💖
• desc — the address of the descriptor you want to map, iykyk
• size — how big the descriptor is, aka the size of the descriptor to map
• dma — a pointer that gets the DMA address back (it's the DMA address return pointer, periodt)
• dma_sz — the adjusted return pointer 👑

---

⭐ RETURN ⭐

0 on success, errno otherwise. that's it, that's the vibe check 😭

ngl, if you get anything back that's not 0, go read your errno and figure out what went wrong. she's telling you something 🧚

---

🦋 SEE ALSO 🦋

kernel file ./drivers/soc/ti/knav_qmss_queue.c plus the whole friend group:

• knav_queue_notify(9)
• knav_queue_open(9)
• knav_queue_close(9)
• knav_queue_device_control(9)
• knav_queue_push(9)
• knav_queue_pop(9)
• knav_pool_create(9)
• knav_pool_destroy(9)
• knav_pool_desc_get(9)
• knav_pool_desc_put(9)
• knav_pool_desc_unmap(9)
• knav_pool_count(9)

---

ok that's the whole page, you ate that 💅 this diva lives in ./drivers/soc/ti and the calendar says October 2026 — so yeah, go map those descriptors, bestie, ily, bye! 🍓💜🎀