spu2_cipher_req_init(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– spu2_cipher_req_init(9) πŸ’–

okay bestie, welcome to the Kernel API Manual page for spu2_cipher_req_init(9) β€” yes we're doing kernel crypto group-chat style, and it's gonna slay. 🫢


✨ NAME ✨

spu2_cipher_req_init builds an skcipher SPU2 request message header, including FMD and OMD. that's the whole assignment, no cap. πŸ’…


✨ SYNOPSIS ✨

u16 spu2_cipher_req_init (u8 *spu_hdr , struct spu_cipher_parms
*cipher_parms );

πŸŽ€ ARGUMENTS πŸŽ€

  • spu_hdr β€” Location of start of SPU request (FMD field) ✨ like, where the SPU request begins, and specifically the FMD field.
  • cipher_parms β€” Parameters describing cipher request πŸ¦‹ your little bundle of cipher request info.

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so this one gets called at setkey time, and its whole job is to initialize a msg header that can be reused for all subsequent skcipher requests. iconic, honestly. πŸ”₯

It constructs the message starting at spu_hdr. The caller should allocate this buffer in DMA-able memory at least SPU_HEADER_ALLOC_LEN bytes long. so yes, DMA-able memory, and at least that many bytes β€” do not skimp, bestie. πŸ’€

this is a "should allocate" situation, not a vibe-check-optional situation. keep it DMA-able and at least SPU_HEADER_ALLOC_LEN bytes. 🫢

🌸 RETURN 🌸

returns the total length of the SPU header (FMD and OMD) in bytes. and if an error occurs, it returns 0. πŸŽ€


πŸ”₯ SEE ALSO πŸ”₯

the Kernel file is literally ./drivers/crypto/bcm/spu2.c, and here's the whole squad of (9) besties β€” every single one, no skips: πŸ’…

okay bye bestie 🫢 β€” source/version ./drivers/crypto/bcm, dated October 2026, for spu2_cipher_req_init(9). periodt πŸ’…βœ¨

πŸ“¦ where this page comes from