qbman_swp_ge...q_coalescing(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

qbman_swp_get_irq_coalescing β€” get the current IRQ coalescing parameters ✨

okay so first things first, bestie: this page is qbman_swp_ge...q_coalescing(9) from the Kernel API Manual (yes the header really truncates it like that, it's giving "name too long for the vibes" and we're not fixing it, we're respecting it πŸ’€). Anyway. The function is qbman_swp_get_irq_coalescing and its whole personality is reading back the IRQ coalescing params, no cap.


🌸 SYNOPSIS 🌸

void qbman_swp_get_irq_coalescing (struct qbman_swp *p , u32
*irq_threshold , u32 *irq_holdoff );

So it returns void β€” nothing comes back at you, it's not that kind of function 🫢 β€” and it takes three things: your portal p, plus two u32 * pointers where the answers get parked.


πŸ¦‹ ARGUMENTS πŸ¦‹

  • p β€” the software portal object. That's your portal, the main character of this whole situation πŸ‘‘
  • irq_threshold β€” interrupt threshold β€” an IRQ is generated when there are more DQRR entries in the portal than the threshold. Lowkey the whole point: cross the line, get an interrupt πŸ”₯
  • irq_holdoff β€” interrupt holdoff (timeout) period in us. It's a timeout, it's in microseconds, it's iconic πŸŽ€

⭐ SEE ALSO ⭐

Kernel file ./drivers/soc/fsl/dpio/qbman-portal.c β€” and honestly the whole friend group shows up here, so let's do roll call πŸ“‹


okay that's the whole page, bestie!! πŸ’– This one lives over in ./drivers/soc/fsl/dpio, dated October 2026, and it's qbman_swp_ge...q_coalescing(9) forever and ever β€” go get those coalescing params, you're gonna eat πŸ“πŸ’…

πŸ“¦ where this page comes from