s5p_set_dma_hashdata(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… s5p_set_dma_hashdata ✨

okay bestie, welcome to the Kernel API Manual page for s5p_set_dma_hashdata(9) β€” yes that's the whole title, yes it's a mouthful, no we're not changing it 🫢


✨ NAME ✨

s5p_set_dma_hashdata β€” start DMA with sg πŸš€

That's it. That's the whole job. It starts the DMA using an sg. Slay.


πŸ¦‹ SYNOPSIS πŸ¦‹

void s5p_set_dma_hashdata (struct s5p_aes_dev *dev , const struct
scatterlist *sg );

notice the void β€” this one gives nothing back, it's a giving function, not a receiving one πŸ˜ŒπŸ’–


🌸 ARGUMENTS 🌸

  • dev β€” the device πŸ’» that's it, that's the descriptor, it's literally just the device, she's the main character
  • sg β€” the scatterlist that's ready to DMA transmit πŸ“€ like she's packed and waiting at the door, fully ready to go
fr fr both of these are the ones you hand over β€” no defaults, no fallbacks, no "guess what I meant". You bring the device and you bring the ready-to-transmit scatterlist. periodt πŸ’…

πŸ‘‘ SEE ALSO πŸ‘‘

okay this next part is a whole friend group so buckle up, I'm listing every single one because nobody gets left behind at this party πŸŽ€

The kernel file in question is ./drivers/crypto/s5p-sss.c ✨ and it hangs out with:

like… that's the whole gc right there 😭 every single one, no cap, iykyk πŸ’œ


and that's the page bestie!! written from ./drivers/crypto, dated October 2026 β€” go start some DMA, you've got this πŸ§šβ€β™€οΈβ­πŸ’–

πŸ“¦ where this page comes from