spu2_assoc_resp_len(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

spu2_assoc_resp_len(9) πŸ’…

okay so bestie, welcome to the Kernel API Manual β€” this page is literally all about spu2_assoc_resp_len(9), and it’s giving β€œtiny helper, big AAD2 buffer energy” ✨.

πŸ’– NAME πŸ’–

spu2_assoc_resp_len β€” Determine the size of the AAD2 buffer needed to catch associated data in a SPU2 output packet. No cap, that’s the whole assignment 🫢.

✨ SYNOPSIS ✨

u32 spu2_assoc_resp_len (enum spu_cipher_mode cipher_mode , unsigned int assoc_len , unsigned int iv_len , bool is_encrypt );

πŸŽ€ ARGUMENTS πŸŽ€

  • cipher_mode β€” cipher mode. That’s it, that’s the vibe πŸ’….
  • assoc_len β€” length of additional associated data, in bytes. (Bytes, bestie β€” keep up 😭.)
  • iv_len β€” length of initialization vector, in bytes. Iconic little length parameter 🌸.
  • is_encrypt β€” true if encrypting. false if decrypt. Periodt.

🌸 RETURN 🌸

It returns the Length of buffer to catch associated data in response β€” yes, that’s the whole return situation, and it ate πŸ”₯.

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./drivers/crypto/bcm/spu2.c β€” and the whole squad:


okay that’s the page, bestie! Source/version: ./drivers/crypto/bcm Β· Date: October 2026 Β· Page: spu2_assoc_resp_len(9) β€” byeeee πŸ’‹βœ¨

πŸ“¦ where this page comes from