pkg/driver_cryptocell_310: allow data to be in ROM on hash update

[Lukas-Luger]

Contribution description

Removal of PSA_ERROR_DATA_INVALID when passing data from ROM into cryptocell_310_common_hash_update.
This is achieved by sequentially copying data from ROM into a buffer and calling a new "continue" function.

Testing procedure

examples/advanced_examples/psa_crypto and tests/sys/psa_crypto_hashes should now work with const messages, as provided in the commit. Tested it with feather-nrf52840-sense and nrf52840dk successfully.

Issues/PRs references

The PSA_ERROR_DATA_INVALID was introduced in #21138.

[Einhornhool]

Why exactly is this being removed again? We only recently introduced this, because hash operations with inputs longer than 64 bytes failed, because read operations from ROM took too long for the accelerator.

Also, as Mikolai wrote in his PR, CryptoCell officially only supports DMA from RAM.

[mguetschow]

Thanks for pinging @Einhornhool.

#21138 is one slightly hacky solution to the problem, by simply disallowing data to be ROM.

This PR uses a different approach, which is possible for all cryptographic operations that allow multi-part operation: It copies the content of the ROM buffer chunk-wise into a buffer on the stack (in RAM) and passes these chunks individually to the hardware. I think that's an elegant solution (as long as the buffer is not too large for the stack).

[Einhornhool]

Ah, I see. Then it looks good to me :)

[mguetschow]

Looks good, thanks! Some nits below.

[mguetschow]

Looks good then, please squash!

[riot-ci]

Murdock results

✔️ PASSED

daf814e pkg/driver_cryptocell_310: allow data to be in ROM on hash update

Success	Failures	Total	Runtime
10271	0	10271	08m:16s

Artifacts

• Documentation preview

[mguetschow]

Could you please rebase on current master (which has the example's directory renamed again) and reformat the commit message according to RIOT's Contributing Guide?

[mguetschow]

Thanks!