[nrf noup] tests: crypto: Add overlay for new board

[degjorva]

Add ENTROPY_GENERATOR=y in overlay
This fixes an error where a trng source is not included in ncs. Addition of this for other L series devices is also a noup.

[nordic-piks]

You can avoid noup by adding test here: https://github.com/nrfconnect/sdk-nrf/tree/main/tests/zephyr
ie. reference original code and settings, specify custom sample.yaml for ls05 and board overlay.
Then, original zephyr test will stay in quarantine (until upmerging ls05 board).

[degjorva]

@nordic-piks This entire config is a noup though, not just for ls05, but for all 54L boards. Or can I do that for all of these boards?

[nordic-piks]

@nordic-piks This entire config is a noup though, not just for ls05, but for all 54L boards. Or can I do that for all of these boards?

You can make nrf.extended test for any platform. Up to you. Just adding new overlay as noup is probably no a big problem during upmerge.

[tomi-font]

Make this a fixup commit (@Vge0rge does it) so it gets squashed together with the original noup when a history cleanup is made?

[Vge0rge]

Make this a fixup commit (@Vge0rge does it) so it gets squashed together with the original noup when a history cleanup is made?

You mean the nrf-quash tag. Indeed it is a good idea to have this here.
The format is simple:

[nrf noup] You commit here
<empty line>
nrf-squash! [nrf noup]  the original noup commit title
<empty line>
Your description here

[degjorva]

@piotrkoziar I could not get it to work using your setup, as when adding it to sdk-nrf we also include PSA_CRYPTO_PROVIDER_CUSTOM when trying to run with this. Which breaks the build. I created a draft here: nrfconnect/sdk-nrf#26373 which uses your way to exclude 54L series devices from these tests. As it is not a supported use case I think this makes the most sense. Is that an acceptable solution for you?

If it is I will open a revert pr the noups for all 54L series devices and close this PR.