ec3c3f153b
This commit introduces a common API for managing nRF53 SoC network CPU Force-OFF state. From the application CPU point of view, the network CPU is a shared resource used by multiple users. The current solution where every user controls the network core state directly leads to dependencies between users and does not scale well. To address this problem there should be a single entity responsible for controlling the network CPU Force-OFF signal. This commit introduces such module. Signed-off-by: Jędrzej Ciupis <jedrzej.ciupis@nordicsemi.no>
20 lines
771 B
CMake
20 lines
771 B
CMake
# SPDX-License-Identifier: Apache-2.0
|
|
|
|
zephyr_library_sources(soc.c)
|
|
zephyr_include_directories(.)
|
|
|
|
zephyr_library_sources_ifdef(CONFIG_SOC_NRF53_CPUNET_MGMT nrf53_cpunet_mgmt.c)
|
|
zephyr_library_sources_ifdef(CONFIG_NRF53_SYNC_RTC sync_rtc.c)
|
|
|
|
if (CONFIG_SOC_NRF53_ANOMALY_160_WORKAROUND_NEEDED AND
|
|
NOT CONFIG_SYS_CLOCK_EXISTS)
|
|
message(WARNING "
|
|
Your application may be affected by the anomaly 160 that concerns the
|
|
nRF5340 SoC. The related workaround cannot be applied, because your
|
|
application has the system clock disabled (CONFIG_SYS_CLOCK_EXISTS=n).
|
|
Consider enabling the system clock to apply the workaround.
|
|
" "
|
|
At your own risk, you can suppress this warning by setting
|
|
CONFIG_SOC_NRF53_ANOMALY_160_WORKAROUND_NEEDED=n.")
|
|
endif()
|