Skip to content
Permalink
Browse files

kconfig: Fix nrf91 NONSECURE dependency

It is expressed that the BOARD depends on whether NONSECURE is enabled
or not. But it is the other way around. Depending on the selected
board, it may or may not be possible to enable/disable NONSECURE.

The dependency is going in the wrong direction, this reversed edge is
observed to be able to create a cycle in the dependency graph.

Fix the dependency by removing it.

It is left as future work to enforce that enabling/disabling NONSECURE
is done in a way that is compatible with selecting
BOARD_NRF9160_PCA10090 vs BOARD_NRF9160_PCA10090NS.

Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
  • Loading branch information...
SebastianBoe authored and carlescufi committed Aug 6, 2019
1 parent 6dceb49 commit 34180d376f23e13487b8e78e327b5f68a225f1a4
Showing with 0 additions and 2 deletions.
  1. +0 −2 boards/arm/nrf9160_pca10090/Kconfig.board
@@ -8,10 +8,8 @@ if SOC_NRF9160_SICA

config BOARD_NRF9160_PCA10090
bool "nRF9160 PCA10090"
depends on !TRUSTED_EXECUTION_NONSECURE

config BOARD_NRF9160_PCA10090NS
bool "nRF9160 PCA10090 non-secure"
depends on TRUSTED_EXECUTION_NONSECURE

endif # SOC_NRF9160_SICA

0 comments on commit 34180d3

Please sign in to comment.
You can’t perform that action at this time.