__udma_alloc_gp_rflow_range(9)

🌸 NAME 🌸

__udma_alloc_gp_rflow_range — alloc range of GP RX flows

okay bestie, welcome to the Kernel API Manual entry for __udma_alloc_gp_rflow_range(9) 💖 this one is all about grabbing a range of GP RX flows, and yes it’s a kernel API thing — we love that for us ✨

✨ SYNOPSIS ✨

int __udma_alloc_gp_rflow_range (struct udma_dev *ud , int from , int
       cnt );

🎀 ARGUMENTS 🎀

• ud — UDMA device. That’s the device we’re working with, periodt 💅
• from — Start the search from this flow id number. Like, the starting point for the hunt 🔎
• cnt — Number of consecutive flow ids to allocate. Gotta get that many in a row, no cap 💯

💅 DESCRIPTION 💅

So the vibe is: allocate a range of RX flow ids for future use 🫶 those flows can be requested only using explicit flow id number — iykyk, explicit flow id number only.

If from is set to -1, it will try to find first free range 👑 If from is positive value, it will force allocation only of the specified range of flows. Like, it’s giving “we’re doing this exact range or nothing” 💅

Returns -ENOMEM if can’t find free range 😭 -EEXIST if requested range is busy 💀 -EINVAL if wrong input values passed 🙈 and it returns flow id on success 🌈✨

🦋 SEE ALSO 🦋

• Kernel file ./drivers/dma/ti/k3-udma.c
• udma_get_tr_counters(9)

okay bye bestie 🫶 this page’s source/version is ./drivers/dma/ti, dated October 2026, and it’s the manual entry for __udma_alloc_gp_rflow_range(9) — periodt 💅