xilinx_dpdma...fy_no_ostand(9)
π xilinx_dpdma_chan_notify_no_ostand(9) β from the Kernel API Manual, bestie π
Okay so β¨ welcome to the Kernel API Manual β¨, and today's main character is xilinx_dpdma_chan_notify_no_ostand β yes that's a whole mouthful, yes it ate, and yes we're gonna get through it together. Buckle up π¦
πΈ NAME πΈ
xilinx_dpdma_chan_notify_no_ostand β literally just "Notify no outstanding transaction event". That's the whole vibe. It tells everybody waiting that there's officially Nothing Outstanding anymore π
β¨ SYNOPSIS β¨
int xilinx_dpdma_chan_notify_no_ostand(struct xilinx_dpdma_chan *chan);
One function, one argument, returns an int. Clean, minimal, iconic π
π ARGUMENTS π
chanβ the DPDMA channel. That's it. That's the argument. She's the one we're notifying about π«Ά
π₯ DESCRIPTION π₯
So here's the tea β β this function notifies the waiters for the no-outstanding event, so those waiters can stop the channel safely. No chaos, no mess, just a clean shutdown vibe check β
You're supposed to call this when the 'no outstanding' interrupt gets generated. Like, that's its moment. That's its whole purpose π
Now the important part, don't skip this π β the 'no outstanding' interrupt is disabled, and it should be re-enabled when this event is handled. So it's giving "turn me back on when you're done", okay?
And if the channel status register still shows some number of outstanding transactions? Then nope β the interrupt remains enabled. It stays on. It's not leaving the group chat π
π RETURN π
0on success π β we love a zero, zero is the bestie we want- On failure,
-EWOULDBLOCKif there's still outstanding transaction(s) π β like, hello?? there's still stuff pending?? cannot deal
π SEE ALSO π
Right, grab a snack π because this list is long and we are not skipping a single one β every single reference is coming with us:
Kernel file ./drivers/dma/xilinx/xilinx_dpdma.c, plus:
struct xilinx_dpdma_hw_desc(9)struct xilinx_dpdma_sw_desc(9)struct xilinx_dpdma_tx_desc(9)struct xilinx_dpdma_chan(9)struct xilinx_dpdma_device(9)xilinx_dpdma_sw_desc_set_dma_addrs(9)xilinx_dpdma_chan_alloc_sw_desc(9)xilinx_dpdma_chan_free_sw_desc(9)xilinx_dpdma_chan_dump_tx_desc(9)xilinx_dpdma_chan_alloc_tx_desc(9)xilinx_dpdma_chan_free_tx_desc(9)xilinx_dpdma_chan_prep_cyclic(9)xilinx_dpdma_chan_prep_interleaved_dma(9)xilinx_dpdma_chan_enable(9)xilinx_dpdma_chan_disable(9)xilinx_dpdma_chan_pause(9)xilinx_dpdma_chan_unpause(9)xilinx_dpdma_chan_queue_transfer(9)xilinx_dpdma_chan_ostand(9)xilinx_dpdma_chan_wait_no_ostand(9)xilinx_dpdma_chan_poll_no_ostand(9)xilinx_dpdma_chan_stop(9)xilinx_dpdma_chan_done_irq(9)xilinx_dpdma_chan_vsync_irq(9)xilinx_dpdma_chan_err(9)xilinx_dpdma_chan_handle_err(9)xilinx_dpdma_alloc_chan_resources(9)xilinx_dpdma_free_chan_resources(9)xilinx_dpdma_terminate_all(9)xilinx_dpdma_synchronize(9)xilinx_dpdma_err(9)xilinx_dpdma_handle_err_irq(9)xilinx_dpdma_enable_irq(9)xilinx_dpdma_disable_irq(9)xilinx_dpdma_chan_err_task(9)
Lowkey a whole ecosystem in here π β if you're deep in the Xilinx DPDMA driver, bestie, you're gonna be reading a lot of these. Hydrate first π§
And that's the page!! π«Ά Sourced from ./drivers/dma/xilinx, dated October 2026, and brought to you by the same truncated-title energy as xilinx_dpdma...fy_no_ostand(9) β iykyk πβ¨π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms