Searched full:risk (Results 1 – 25 of 66) sorted by relevance
123
| /Zephyr-latest/dts/bindings/test/ |
| D | vnd,non-deprecated-label.yaml | 5 This can be used when we need a label property in tests without risk
|
| /Zephyr-latest/soc/nordic/nrf53/ |
| D | CMakeLists.txt | 17 At your own risk, you can suppress this warning by setting
|
| /Zephyr-latest/subsys/usb/device/class/dfu/ |
| D | Kconfig | 46 Be aware that upload capability can be a security risk because
|
| /Zephyr-latest/drivers/ethernet/ |
| D | Kconfig.dwmac | 65 memory. A smaller number increases the risk of an overflow and
|
| /Zephyr-latest/modules/hal_nordic/nrfs/ |
| D | CMakeLists.txt | 39 …r Nordic Semiconductor INTERNAL purposes ONLY. Use it with caution due to risk of hardware damage!…
|
| /Zephyr-latest/subsys/net/l2/ppp/ |
| D | Kconfig | 107 execution to the lower layer network stack, with a high risk of
|
| /Zephyr-latest/boards/qemu/cortex_m0/ |
| D | nrf_timer_timer.c | 75 /* First take care of a risk of an event coming from CC being set to in prevent_false_prev_evt()
79 * is no risk of unwanted event. in prevent_false_prev_evt()
|
| /Zephyr-latest/doc/safety/ |
| D | safety_overview.rst | 60 #. **Hazard and Risk Analysis**: The IEC 61508 standard requires a thorough analysis of potential
65 (SIL) to classify the level of risk reduction required for each safety function. The higher the
66 SIL, the greater the level of risk reduction required.
84 implementation of safety-related systems that aims to reduce the risk of accidents and improve
|
| /Zephyr-latest/doc/hardware/peripherals/edac/ |
| D | ibecc.rst | 44 Due to high security risk Error Injection capability should not be enabled for
|
| /Zephyr-latest/tests/kernel/interrupt/src/ |
| D | static_shared_irq.c | 30 * decreasing the risk of build errors appearing due to the in ZTEST()
|
| /Zephyr-latest/tests/subsys/edac/ibecc/ |
| D | README.rst | 37 Due to high security risk Error Injection capability should not be
|
| /Zephyr-latest/drivers/clock_control/ |
| D | Kconfig.nrf | 64 risk.
|
| /Zephyr-latest/doc/security/standards/ |
| D | etsi-303645.rst | 207 risk of automated attacks against a class or type of device.
216 the properties of the technology, risk and usage.
419 shall be unique per device and shall be produced with a mechanism that reduces the risk
468 appropriate to the properties of the technology, risk and usage.
|
| /Zephyr-latest/doc/kernel/services/other/ |
| D | atomic.rst | 49 incremented atomically, there is no risk that it will become corrupted
|
| /Zephyr-latest/doc/contribute/ |
| D | bin_blobs.rst | 170 Allowing arbitrary library blobs carries a risk of degrading the degree to
175 To mitigate this risk, the scope of upstream library blobs is limited. The
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | blob_cli.rst | 72 groups. This can lead to longer recovery periods at the end of each block, and increases the risk of
|
| D | core.rst | 60 calling :c:func:`bt_mesh_rpl_pending_store` may reduce a risk of security
|
| /Zephyr-latest/drivers/counter/ |
| D | counter_nrfx_timer.c | 158 /* First take care of a risk of an event coming from CC being set to in set_cc()
173 * it is assumed that there is a risk of setting value too late in set_cc()
|
| D | counter_nrfx_rtc.c | 253 /* First take care of a risk of an event coming from CC being set to in set_cc()
257 * is no risk of unwanted event. in set_cc()
277 * it is assumed that there is a risk of setting value too late in set_cc()
|
| D | counter_gd32_timer.c | 225 /* First take care of a risk of an event coming from CC being set to in set_cc()
238 * it is assumed that there is a risk of setting value too late in set_cc()
|
| /Zephyr-latest/arch/arm/core/ |
| D | userspace.S | 125 * CONFIG_MPU_STACK_GUARD). There is a risk of actually overflowing the
126 * stack while doing the re-programming. We minimize the risk by placing
130 * Note that the risk for overflow is higher if using the normal thread
|
| /Zephyr-latest/subsys/net/ip/ |
| D | Kconfig.tcp | 45 execution to the lower layer network stack, with a high risk of
|
| /Zephyr-latest/soc/nxp/imx/imx8m/m7/ |
| D | soc.c | 90 * on M7 side, otherwise it would have a risk to make the SOC hang. in SOC_ClockInit()
|
| /Zephyr-latest/drivers/led_strip/ |
| D | ws2812_gpio.c | 109 * of slack time between bits before we risk the in send_buf()
|
| /Zephyr-latest/lib/utils/ |
| D | base64.c | 179 * without risk of integer overflow in n: in base64_decode()
|
123
