spum_cipher_req_init(9)

spum_cipher_req_init(9) — Kernel API Manual ✨

💖 NAME 💖

the way that spum_cipher_req_init builds a SPU request message header, up to and including the BD header — iconic behavior, periodt. 💅

🌸 SYNOPSIS 🌸

ngl bestie, here's the signature, copy it exactly:

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

🎀 ARGUMENTS 🎀

• spu_hdr — start of the SPU request header (MH). literally the beginning of the header buffer, main character energy. ✨
• cipher_parms — parameters that describe the cipher request. it's giving "all the cipher-request deets," lowkey essential. 💖

🦋 DESCRIPTION 🦋

okay so this function constructs the message starting at spu_hdr. The caller should allocate this buffer in DMA-able memory, and it has to be at least SPU_HEADER_ALLOC_LEN bytes long. highkey this is the vibe check: DMA-able memory, minimum SPU_HEADER_ALLOC_LEN bytes, no cap, fr fr. The function ate that, ngl. 🫶

🔥 RETURN 🔥

Returns the length of the SPU header in bytes. If an error occurs, it returns 0. That 0 is the "not me getting an error" signal, so don't ignore it — obsessed with clear error signals, honestly. 😭

💜 SEE ALSO 💜

Kernel file ./drivers/crypto/bcm/spu.c — yes, that's the spot. Then go check these besties too (iykyk):

• 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_assoc_resp_len(9)
• spum_aead_ivlen(9)
• spum_hash_type(9)
• spum_digest_size(9)
• spum_create_request(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)

mwah 💋 this page's source/version bit is ./drivers/crypto/bcm and the date is October 2026 — bye bestie, slay your cipher requests! 🫶👑