stm32_bsec_optee_ta_read(9)
β¨ stm32_bsec_optee_ta_read β Kernel API Manual β¨
πΈ NAME πΈ
stm32_bsec_optee_ta_read β nvmem read access using TA client driver π
Okay bestie, this is the function that does an nvmem read through the TA client driver. Itβs giving βread energyβ and itβs literally sitting in the Kernel API Manual. π«Ά
π SYNOPSIS π
int stm32_bsec_optee_ta_read (struct tee_context *ctx , unsigned int
offset , void *buf , size_t bytes );
π ARGUMENTS π
ctxβ the OP-TEE context provided bystm32_bsec_optee_ta_open. Thatβs the handshake, bestie. π€offsetβ nvmem offset.bufβ buffer to fill withnvemvalues. Not me noticing the manpage saysnvemand notnvmemβ keeping it exactly as written, periodt. πbytesβ number of bytes to read.
π₯ RETURN π₯
On success, 0. On failure, -errno. No cap. π
π¦ SEE ALSO π¦
- Kernel file
./drivers/nvmem/stm32-bsec-optee-ta.hβ the header bestie, go look. π stm32_bsec_optee_ta_open(9)stm32_bsec_optee_ta_close(9)stm32_bsec_optee_ta_write(9)
Those are the sibling functions, and yes, the whole squad is here. π
π Thatβs the whole page, bestie. Every argument, return value, file path, and SEE ALSO reference is here β no facts lost, only vibes added. β¨
Cute sign-off: source/version: ./drivers/nvmem β’ date: October 2026 β mwah ππ
π¦ 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