spum_assoc_resp_len(9)

🦋 spum_assoc_resp_len(9) — Kernel API Manual 🦋

Ok bestie, welcome to the Kernel API Manual entry for spum_assoc_resp_len(9) — yes, that’s the whole manual name right there, folded in like a little name tag at the party 💖

---

✨ NAME ✨

spum_assoc_resp_len — determine the size of the receive buffer required to catch associated data. Literally the vibe check for how much room you need, bestie 🎀

---

🌸 SYNOPSIS 🌸

u32 spum_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, bestie. That’s the mode vibe 🔥
• assoc_len — length of associated data, in bytes. Count ’em 💖
• iv_len — length of IV, in bytes. Yep, bytes again 🎀
• is_encrypt — true if encrypting. false if decrypting. Iconic boolean behavior, no cap 💅

---

⭐ RETURN ⭐

Length of associated data in response message, in bytes. That’s the answer, bestie 🫶

---

🌈 SEE ALSO 🌈

Kernel file: ./drivers/crypto/bcm/spu.c

The whole function bestie squad, all here, all accounted for:

• spum_ns2_ctx_max_payload(9)
• spum_nsp_ctx_max_payload(9)
• spum_response_hdr_len(9)
• spum_hash_pad_len(9)
• spum_gcm_ccm_pad_len(9)
• spum_aead_ivlen(9)
• spum_hash_type(9)
• spum_digest_size(9)
• spum_create_request(9)
• spum_cipher_req_init(9)
• spum_cipher_req_finish(9)
• spum_request_pad(9)
• spum_xts_tweak_in_payload(9)
• spum_tx_status_len(9)
• spum_rx_status_len(9)
• spum_status_process(9)
• spum_ccm_update_iv(9)
• spum_wordalign_padlen(9)

---

Catch u later, bestie 💖 — source/version: ./drivers/crypto/bcm, dated October 2026, for spum_assoc_resp_len(9) 🫶