ocs_hcu_hw_cfg(9)
okay bestie, so this little cutie is ocs_hcu_hw_cfg(9) from the Kernel API Manual, and she's the one who sets up your HCU hardware. literally the getting-ready-with-me of kernel calls π
π NAME π
ocs_hcu_hw_cfg β configure the HCU hardware. that's it, that's the whole vibe. she configures. periodt. β¨
π¦ SYNOPSIS π¦
int ocs_hcu_hw_cfg (struct ocs_hcu_dev *hcu_dev , enum ocs_hcu_algo algo
, bool use_hmac );
like, she takes three things and gives you back an int. no cap, that's the whole signature. π«Ά
πΈ ARGUMENTS πΈ
hcu_devβ the HCU device you wanna configure, bestie. the one. the main character. πalgoβ the algorithm the HCU device is gonna be using. which one? that's between you andenum ocs_hcu_algo. π§use_hmacβ aboolasking the real questions: are we using HW HMAC or not? yes or no, no in-between. π
β RETURN β
0β slay, it worked, success. π- negative error code β not slay. something went wrong, and that's the tea. π
π SEE ALSO π
the whole friend group, fr fr β they're all in the kernel file ./drivers/crypto/intel/keembay/ocs-hcu.c:
struct ocs_hcu_dma_entry(9)struct ocs_hcu_dma_list(9)ocs_hcu_wait_busy(9)ocs_hcu_get_intermediate_data(9)ocs_hcu_set_intermediate_data(9)ocs_hcu_clear_key(9)ocs_hcu_write_key(9)ocs_hcu_ll_dma_start(9)ocs_hcu_hash_init(9)ocs_hcu_hash_update(9)ocs_hcu_hash_finup(9)ocs_hcu_hash_final(9)ocs_hcu_digest(9)ocs_hcu_hmac(9)
like go read those too, they're iconic, iykyk. π
lowkey reminder: she returns 0 on success and a negative error code otherwise β so always vibe check that return value, bestie. don't just ignore it. π
that's the whole page, mwah π β brought to you by ./drivers/crypto/intel/keembay, October 2026, and of course our girl ocs_hcu_hw_cfg(9). see you in the kernel, bestie πβ¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms