ocs_hcu_hash_update(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’« ocs_hcu_hash_update(9) πŸ’«

okay so bestie, welcome to the kernel API manual for ocs_hcu_hash_update β€” that's the OCS HCU one, section 9, straight out of the Kernel API Manual. she's a hashing queen and honestly? iconic.


✨ NAME ✨

ocs_hcu_hash_update β€” literally just performs one hashing iteration. that's it. that's the whole vibe. πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

int ocs_hcu_hash_update (struct ocs_hcu_dev *hcu_dev , struct
ocs_hcu_hash_ctx *ctx , const struct ocs_hcu_dma_list *dma_list );

three args, one int coming back at you. slay. πŸŽ€


🌸 ARGUMENTS 🌸

  • hcu_dev β€” the struct ocs_hcu_dev * pointing at the OCS HCU device you wanna use. like, which one of the devices, bestie. pick one. 🫢
  • ctx β€” the struct ocs_hcu_hash_ctx *, aka the OCS HCU hashing context. it's giving "the memory of what we're hashing so far." ✨
  • dma_list β€” the const struct ocs_hcu_dma_list * that maps the input data to process. think of it as the map that tells the hardware where the actual bytes live. lowkey essential. πŸ—ΊοΈ

πŸ”₯ RETURN πŸ”₯

0 on success, and a negative error code otherwise. no cap β€” success is literally zero and anything else means something went sideways. 😭


πŸ‘‘ SEE ALSO πŸ‘‘

kernel file ./drivers/crypto/intel/keembay/ocs-hcu.c β€” yes, that's where all the lore lives 🧚

the whole friend group, in order:


ok that's the whole page πŸ’– no skipped options, no deleted references, we keep every detail in this house. periodt.

sign-off time πŸŽ€ this little masterpiece lives under ./drivers/crypto/intel/keembay, dated October 2026 β€” and it's page ocs_hcu_hash_update(9) of the Kernel API Manual. go hash something, bestie πŸ’…βœ¨πŸ¦‹

πŸ“¦ where this page comes from