cc_sram_alloc(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– cc_sram_alloc(9) πŸ’–

okay so bestie, welcome to the Kernel API Manual ✨ this one's a little function called cc_sram_alloc and honestly it's giving "tiny but crucial" energy. Let's get into it πŸŽ€


🌸 NAME 🌸

cc_sram_alloc β€” allocate a buffer from the SRAM pool πŸ¦‹

Like, it grabs you some space out of the SRAM pool. That's the whole vibe. Iconic, honestly.


✨ SYNOPSIS ✨

u32 cc_sram_alloc (struct cc_drvdata *drvdata , u32 size );

yeah that's the whole call, no cap πŸ‘‘


🫢 ARGUMENTS 🫢

  • drvdata β€” the associated device driver context 🌈 like, the driver's whole little world, passed in so the function knows who's asking.
  • size β€” the requested bytes to allocate πŸ’… tell it how many bytes you want, it goes and finds them.

πŸ”₯ RETURN πŸ”₯

It hands back an address offset in SRAM ✨ ...or NULL_SRAM_ADDR if it failed 😭 so yeah, check your return value, bestie, fr fr β€” that's your vibe check right there.


πŸ‘‘ SEE ALSO πŸ‘‘

go read those, iykyk πŸ§šβ€β™€οΈ


and that's the page!! periodt πŸ’œ this little gem lives in ./drivers/crypto/ccree and the docs are dated October 2026 πŸ“ mwah, love u, go allocate responsibly πŸ’–πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from