spu2_gcm_ccm_pad_len(9)

💅 spu2_gcm_ccm_pad_len(9) 💅

okay bestie, welcome to the Kernel API Manual page for spu2_gcm_ccm_pad_len(9). This one is short and sweet, and it's giving “hardware handles the padding.” ✨

🌸 NAME 🌸

spu2_gcm_ccm_pad_len — Determine the length of GCM/CCM padding for either the AAD field or the data.

✨ SYNOPSIS ✨

u32 spu2_gcm_ccm_pad_len (enum spu_cipher_mode cipher_mode , unsigned
       int data_size );

🎀 ARGUMENTS 🎀

• cipher_mode — Unused. Like, genuinely unused, no cap.
• data_size — Unused. Also unused, bestie.

👑 RETURN 👑

• 0 — Unlike SPU-M, SPU2 hardware does any GCM/CCM padding required.

So yeah, the return value is 0. The reason is right there: unlike SPU-M, SPU2 hardware does any GCM/CCM padding required. Periodt. 💅

🦋 SEE ALSO 🦋

go read these next, bestie:

• Kernel file ./drivers/crypto/bcm/spu2.c
• spu2_cipher_xlate(9)
• spu2_hash_xlate(9)
• spu2_fmd_init(9)
• spu2_fmd_ctrl0_write(9)
• spu2_fmd_ctrl1_write(9)
• spu2_fmd_ctrl2_write(9)
• spu2_fmd_ctrl3_write(9)
• spu2_ctx_max_payload(9)
• spu2_payload_length(9)
• spu2_response_hdr_len(9)
• spu2_hash_pad_len(9)
• spu2_assoc_resp_len(9)
• spu2_aead_ivlen(9)
• spu2_hash_type(9)
• spu2_digest_size(9)
• spu2_create_request(9)
• spu2_cipher_req_init(9)
• spu2_cipher_req_finish(9)
• spu2_request_pad(9)
• spu2_xts_tweak_in_payload(9)
• spu2_tx_status_len(9)
• spu2_rx_status_len(9)
• spu2_status_process(9)
• spu2_ccm_update_iv(9)
• spu2_wordalign_padlen(9)

xoxo, your kernel bestie 💖 — from ./drivers/crypto/bcm, October 2026, page spu2_gcm_ccm_pad_len(9) in the Kernel API Manual. mwah 🫶