@@ -83,17 +83,6 @@ SECTION_SUBSEC_FUNC(TEXT,_reset_section,__start)
83
83
#endif /* CONFIG_INIT_ARCH_HW_AT_BOOT */
84
84
85
85
#if defined(CONFIG_PM_S2RAM)
86
- #if DT_NODE_EXISTS(DT_NODELABEL(pm_s2ram_stack)) &&\
87
- DT_NODE_HAS_COMPAT(DT_NODELABEL(pm_s2ram_stack), zephyr_memory_region)
88
- /* In certain scenarios, the interrupt stack is actually not safe to overwrite.
89
- * For example, when MCUboot is used, the bootloader's "z_interrupt_stack" and the
90
- * loaded image's "z_interrupt_stacks" are NOT at the same address, and writing to
91
- * the former would corrupt unrelated data from the loaded image. To support such
92
- * scenarios, if the Device Tree provides a specially named "zephyr,memory-region",
93
- * use it as the stack to run arch_pm_s2ram_resume instead of the interrupt stack.
94
- */
95
- ldr r0, =DT_REG_ADDR(DT_NODELABEL(pm_s2ram_stack)) + DT_REG_SIZE(DT_NODELABEL(pm_s2ram_stack))
96
- #else
97
86
/*
98
87
* Temporarily set MSP to interrupt stack so that arch_pm_s2ram_resume can
99
88
* use stack for calling pm_s2ram_mark_check_and_clear.
@@ -106,7 +95,6 @@ SECTION_SUBSEC_FUNC(TEXT,_reset_section,__start)
106
95
* a short while, there is no change in behavior in either of the paths.
107
96
*/
108
97
ldr r0, =z_interrupt_stacks + CONFIG_ISR_STACK_SIZE + MPU_GUARD_ALIGN_AND_SIZE
109
- #endif
110
98
msr msp, r0
111
99
112
100
bl arch_pm_s2ram_resume
0 commit comments