set_dout_type(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… set_dout_type(9) β€” the Kernel API Manual, but make it a vibe ✨

okay so picture this: you're deep in the Kernel API Manual and you just need to tell a hardware descriptor what its DOUT situation is. That's the whole plot. No cap, this little function is the main character of exactly one job and it does not miss. 🫢


🌸 NAME 🌸

set_dout_type β€” Set the DOUT field of a HW descriptor πŸ’–

Like, literally. It sets the DOUT field. Of a HW descriptor. That's the assignment and it ate. πŸ‘‘


✨ SYNOPSIS ✨

void set_dout_type (struct cc_hw_desc *pdesc , enum cc_dma_mode dma_mode
, dma_addr_t addr , u32 size , enum cc_axi_sec axi_sec );

returns void btw, so don't go looking for a return value, she gives you nothing back and that's iconic of her. πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • pdesc β€” Pointer to the HW descriptor struct. This is the struct, the one you're decorating. 🌈
  • dma_mode β€” The DMA mode, and the options are: NO_DMA, SRAM, DLLI, MLLI, CONSTANT. Pick your fighter. ⭐
  • addr β€” The DOUT address. Where the data's going, fr fr. πŸ¦‹
  • size β€” Data size in bytes. Yes, bytes. Not vibes, bytes. 😭
  • axi_sec β€” The AXI secure bit. πŸ”₯

🧚 SEE ALSO 🧚

Kernel file: ./drivers/crypto/ccree/cc_hw_queue_defs.h

And the whole friend group, all showing up to support:


bestie reminder: the page name is set_dout_type(9), so if you're grepping for her, that's the key. πŸ”‘

and that's the whole page, mwah πŸ’‹ β€” brought to you straight outta ./drivers/crypto/ccree, dated October 2026, and yeah, the header said set_dout_type(9) and the footer said set_dout_type(9) too because she's consistent like that. πŸŽ€βœ¨

πŸ“¦ where this page comes from