spu_functions_register(9)

🎀 NAME 🎀

okay so bestie, this is spu_functions_register from the Kernel API Manual, and it's here to specify hardware-specific SPU functions based on the SPU type read from the device tree. periodt. 💅

✨ SYNOPSIS ✨

void spu_functions_register (struct device *dev , enum spu_spu_type
spu_type , enum spu_spu_subtype spu_subtype );

💅 ARGUMENTS 💅

• dev — device structure, the whole device bestie this call is about 🫶
• spu_type — SPU hardware generation, aka the era/flavor of the hardware ✨
• spu_subtype — SPU hardware version, the specific little variant 🎀

🌈 SEE ALSO 🌈

For the full lore, the kernel file ./drivers/crypto/bcm/cipher.c is in the mix, plus this whole crew:

• select_channel(9)
• spu_skcipher_rx_sg_create(9)
• spu_skcipher_tx_sg_create(9)
• handle_skcipher_req(9)
• handle_skcipher_resp(9)
• spu_ahash_rx_sg_create(9)
• spu_ahash_tx_sg_create(9)
• handle_ahash_req(9)
• spu_hmac_outer_hash(9)
• ahash_req_done(9)
• handle_ahash_resp(9)
• spu_aead_rx_sg_create(9)
• spu_aead_tx_sg_create(9)
• handle_aead_req(9)
• handle_aead_resp(9)
• spu_chunk_cleanup(9)
• finish_req(9)
• spu_rx_callback(9)
• skcipher_enqueue(9)
• spu_no_incr_hash(9)
• aead_gcm_esp_setkey(9)
• rfc4543_gcm_esp_setkey(9)
• aead_ccm_esp_setkey(9)
• spu_mb_init(9)

bye bestie 💖 — source/version ./drivers/crypto/bcm, date October 2026, and spu_functions_register(9) is signing off 🎀