Home
last modified time | relevance | path

Searched refs:guard (Results 1 – 25 of 39) sorted by relevance

12

/Zephyr-Core-3.5.0/drivers/counter/
Dcounter_rpi_pico_timer.c135 static int counter_rpi_pico_timer_set_guard_period(const struct device *dev, uint32_t guard, in counter_rpi_pico_timer_set_guard_period() argument
140 __ASSERT_NO_MSG(guard < counter_rpi_pico_timer_get_top_value(dev)); in counter_rpi_pico_timer_set_guard_period()
142 data->guard_period = guard; in counter_rpi_pico_timer_set_guard_period()
Dcounter_smartbond_timer.c282 static int counter_smartbond_set_guard_period(const struct device *dev, uint32_t guard, in counter_smartbond_set_guard_period() argument
288 __ASSERT_NO_MSG(guard < counter_smartbond_get_top_value(dev)); in counter_smartbond_set_guard_period()
290 data->guard_period = guard; in counter_smartbond_set_guard_period()
Dcounter_nrfx_timer.c306 static int set_guard_period(const struct device *dev, uint32_t guard, in set_guard_period() argument
311 __ASSERT_NO_MSG(guard < get_top_value(dev)); in set_guard_period()
313 data->guard_period = guard; in set_guard_period()
Dcounter_ifx_cat1.c475 static int ifx_cat1_counter_set_guard_period(const struct device *dev, uint32_t guard, in ifx_cat1_counter_set_guard_period() argument
480 __ASSERT_NO_MSG(guard < ifx_cat1_counter_get_top_value(dev)); in ifx_cat1_counter_set_guard_period()
484 data->guard_period = guard; in ifx_cat1_counter_set_guard_period()
Dcounter_gd32_timer.c372 uint32_t guard, uint32_t flags) in counter_gd32_timer_set_guard_period() argument
376 __ASSERT_NO_MSG(guard < counter_gd32_timer_get_top_value(dev)); in counter_gd32_timer_set_guard_period()
378 data->guard_period = guard; in counter_gd32_timer_set_guard_period()
Dcounter_ll_stm32_timer.c527 static int counter_stm32_set_guard_period(const struct device *dev, uint32_t guard, in counter_stm32_set_guard_period() argument
533 __ASSERT_NO_MSG(guard < counter_stm32_get_top_value(dev)); in counter_stm32_set_guard_period()
535 data->guard_period = guard; in counter_stm32_set_guard_period()
Dcounter_nrfx_rtc.c574 static int set_guard_period(const struct device *dev, uint32_t guard, in set_guard_period() argument
579 data->guard_period = guard; in set_guard_period()
/Zephyr-Core-3.5.0/tests/drivers/counter/maxim_ds3231_api/src/
Dtest_counter.c527 uint32_t guard = counter_us_to_ticks(dev, 200); in test_late_alarm_instance() local
535 err = counter_set_guard_period(dev, guard, in test_late_alarm_instance()
577 uint32_t guard = counter_us_to_ticks(dev, 200); in test_late_alarm_error_instance() local
584 err = counter_set_guard_period(dev, guard, in test_late_alarm_error_instance()
611 uint32_t guard = counter_get_guard_period(dev, in late_detection_capable() local
613 int err = counter_set_guard_period(dev, guard, in late_detection_capable()
/Zephyr-Core-3.5.0/arch/arc/core/mpu/
DKconfig25 If your core supports that, it is preferred over MPU stack guard.
/Zephyr-Core-3.5.0/tests/drivers/counter/counter_basic_api/src/
Dtest_counter.c657 uint32_t guard = counter_us_to_ticks(dev, 200); in test_late_alarm_instance() local
665 err = counter_set_guard_period(dev, guard, in test_late_alarm_instance()
709 uint32_t guard = counter_us_to_ticks(dev, 200); in test_late_alarm_error_instance() local
716 err = counter_set_guard_period(dev, guard, in test_late_alarm_error_instance()
743 uint32_t guard = counter_get_guard_period(dev, in late_detection_capable() local
745 int err = counter_set_guard_period(dev, guard, in late_detection_capable()
/Zephyr-Core-3.5.0/doc/kernel/usermode/
Dmpu_userspace.rst19 guard (if applicable).
Dmpu_stack_objects.rst30 occur, a fault ensues. The stack guard is defined at the bottom (the lowest
/Zephyr-Core-3.5.0/arch/arm/core/mpu/
DKconfig30 guard, user thread stack, and application memory domains), if the
74 Floating Point (FP) context. The width of the guard is set to
/Zephyr-Core-3.5.0/doc/hardware/porting/
Darch.rst576 * For systems that implement stack protection using a guard memory region,
577 it's possible to overshoot the guard and corrupt adjacent data structures
585 CPU features for this purpose, or special read-only guard regions immediately
615 on write. Reserved memory will be used for the guard region.
622 MMU-based systems should not reserve RAM for the guard region and instead
641 the guard is unnecessary and shouldn't be unconditionally reserved.
645 * The required guard size is variable and depends on context. For example, some
648 completely overshooting a minimally-sized guard and corrupting adjacent
649 memory. Rather than unconditionally reserving a larger guard, the extra
660 system calls. If stack guards are implemented, a stack guard region must
[all …]
/Zephyr-Core-3.5.0/arch/arm/core/
DKconfig194 - the MPU-based stack guard
197 The two stack guard options are mutually exclusive. The
199 prioritized over the MPU-based stack guard. The developer
201 stack guard, if this is desired.
/Zephyr-Core-3.5.0/arch/arm64/core/cortex_r/
DKconfig27 guard, user thread stack, and application memory domains), if the
/Zephyr-Core-3.5.0/arch/x86/core/
DKconfig.intel6479 by preceding all stack areas with a 4K guard page.
DKconfig.ia3273 by preceding all stack areas with a 4K guard page.
/Zephyr-Core-3.5.0/subsys/ipc/ipc_service/lib/
DKconfig.icmsg17 multiple contexts. Mutex is used to guard access to the memory.
/Zephyr-Core-3.5.0/cmake/compiler/gcc/
Dcompiler_flags.cmake164 check_set_compiler_property(APPEND PROPERTY security_canaries -mstack-protector-guard=tls)
166 check_set_compiler_property(APPEND PROPERTY security_canaries -mstack-protector-guard=global)
/Zephyr-Core-3.5.0/arch/riscv/
DKconfig278 The Hardware Stack Protection implements a guard area at the bottom
280 guard area not accessible.
282 This is the size of the guard area. This should be large enough to
/Zephyr-Core-3.5.0/arch/arc/
DKconfig240 - the MPU-based stack guard
243 The two stack guard options are mutually exclusive. The
245 prioritized over the MPU-based stack guard.
/Zephyr-Core-3.5.0/cmake/compiler/arcmwdt/
Dcompiler_flags.cmake174 #no support of -mstack-protector-guard=global"
/Zephyr-Core-3.5.0/doc/hardware/arch/
Darm_cortex_m.rst161 memories, and/or programs a stack-overflow MPU guard at the bottom of the thread's
415 the stack guard (in certain Arm v8-M configurations with :kconfig:option:`CONFIG_MPU_GAP_FILLING`
416 enabled 2 MPU regions are required to implement the guard feature)
496 * a read-only region for the MPU stack guard
/Zephyr-Core-3.5.0/arch/arm64/core/
DKconfig181 by preceding all stack areas with a fixed guard region.

12