mpsl: Add KConfig around forcing RRAM when running from NONSECURE

[martintv]

Since this isn't makes powerconsumption be very high, we can let it only be done when "advanced" bluetotoh features are used.

[NordicBuilder]

CI Information

^{To view the history of this post, click the 'edited' button above}
Build number: 6

Inputs:

Sources:

sdk-nrf: PR head: 5de186623ca56e3ef2585e2926f49534ad6fe6ea

more details

sdk-nrf:

PR head: 5de186623ca56e3ef2585e2926f49534ad6fe6ea
merge base: ca6603db120f1098438bbcb4ff5e17aca37b5665
target head (main): 340b62559c443699988e9f76ca0208232197b802
Diff

Github labels

Enabled	Name	Description
	ci-disabled	Disable the ci execution
	ci-all-test	Run all of ci, no test spec filtering will be done
	ci-force-downstream	Force execution of downstream even if twister fails
	ci-run-twister	Force run twister
	ci-run-zephyr-twister	Force run zephyr twister

List of changed files detected by CI (2)

subsys
│  ├── mpsl
│  │  ├── init
│  │  │  ├── Kconfig
│  │  │  │ mpsl_init.c

Outputs:

Toolchain

Version:
Build docker image:

Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped; ⚠️ Quarantine

• ◻️ Toolchain
• ◻️ Build twister
• ◻️ Integration tests
  • ◻️ test_ble_nrf_config
  • ◻️ test-fw-nrfconnect-ble_samples
  • ◻️ test-fw-nrfconnect-chip
  • ◻️ test-fw-nrfconnect-rs
  • ◻️ test-fw-nrfconnect-fem
  • ◻️ test-fw-nrfconnect-thread-main
  • ◻️ test-sdk-find-my

Disabled integration tests

• • test-fw-nrfconnect-nrf_lrcs_positioning
  • desktop52_verification
  • test-fw-nrfconnect-apps
  • test-fw-nrfconnect-ble_mesh
  • test-fw-nrfconnect-nfc
  • test-fw-nrfconnect-nrf-iot_libmodem-nrf
  • test-fw-nrfconnect-nrf-iot_samples
  • test-fw-nrfconnect-nrf-iot_serial_lte_modem
  • test-fw-nrfconnect-nrf-iot_thingy91
  • test-fw-nrfconnect-nrf-iot_zephyr_lwm2m
  • test-fw-nrfconnect-nrf_crypto
  • test-fw-nrfconnect-ps-main
  • test-fw-nrfconnect-rpc
  • test-fw-nrfconnect-tfm
  • test-low-level
  • test-sdk-audio
  • test-sdk-dfu
  • test-sdk-mcuboot
  • test-sdk-wifi
  • test-secdom-samples-public

Note: This message is automatically posted and updated by the CI

[github-actions]

You can find the documentation preview for this PR here.

[nordicjm]

why not default y when those feature Kconfigs are enabled? instead of just always on?

[martintv]

right now TRUSTED_EXECUTION_NONSECURE is only experimentally supported.
what I want to achive with this KConfig is that I can tell customers who complain that powerconsumption is too high, that they can set this config to =n as long as they know they are not using any of those features. I didnt find nice kconfigs for all those features to use for those features, because some of them get set automaticaly as long as the HW supports them. So then I would have to tell customers how to disable those configs.

Right now I think just doing it this way is the easiest. but when we move TFM support out of experimental, I think we should improve this yes, either by having it as kconfig like this which defaults depending on the features. But we might also do it even fancier, at runtime and only force RRAM on, on links when any of these features are enabled.

Bottom line, I want to merge this now so I can tell customer in NCS 3.2 that uses NS, that they can enable this if they want low power when using bluetooth as long as they dont use any of these features.