Searched full:causing (Results 1 – 25 of 88) sorted by relevance
1234
/Zephyr-latest/dts/bindings/video/ |
D | galaxycore,gc2145.yaml | 14 The RESETn pin is asserted to disable the sensor causing a hard
|
D | ovti,ov7725.yaml | 12 The RESETn pin is asserted to disable the sensor causing a hard
|
D | ovti,ov7670.yaml | 12 The RESETn pin is asserted to disable the sensor causing a hard
|
D | ovti,ov2640.yaml | 12 The RESETn pin is asserted to disable the sensor causing a hard
|
/Zephyr-latest/tests/kernel/context/ |
D | Kconfig | 10 running causing the CPU to awake. With this option we allow for a maximum number of wakes
|
/Zephyr-latest/dts/bindings/display/ |
D | himax,hx8394.yaml | 17 The RESX pin is asserted to disable the sensor causing a hard
|
D | ilitek,ili9806e.yaml | 14 The RESETn pin is asserted to disable the sensor causing a hard
|
D | raydium,rm68200.yaml | 17 The RESETn pin is asserted to disable the sensor causing a hard
|
D | raydium,rm67162.yaml | 17 The RESETn pin is asserted to disable the sensor causing a hard
|
D | orisetech,otm8009a.yaml | 15 The RESETn pin is asserted to disable the sensor causing a hard
|
/Zephyr-latest/boards/nxp/mimxrt1010_evk/ |
D | init.c | 17 * boot, causing a hardfault. This can also be resolved by enabling in SystemInitHook()
|
/Zephyr-latest/dts/bindings/sensor/ |
D | ams,ccs811.yaml | 20 The RESETn pin is asserted to disable the sensor causing a hard
|
/Zephyr-latest/dts/bindings/watchdog/ |
D | ti,tps382x.yaml | 18 connection must be high impedance to prevent it from causing a reset
|
/Zephyr-latest/tests/boards/native_sim/cpu_wait/src/ |
D | main.c | 231 * causing a delay of WASTED_TIME (1ms), so the k_busy_wait() in ZTEST() 247 * causing a delay of WASTED_TIME (1ms), after that, the k_busy_wait() in ZTEST() 264 * causing a delay of WASTED_TIME (1ms), but posix_cpu_hold continues in ZTEST() 280 * causing a delay of WASTED_TIME (1ms), but posix_cpu_hold continues in ZTEST()
|
/Zephyr-latest/soc/nxp/mcx/mcxw/ |
D | mcxw71_platform_init.S | 12 * to prevent ECC causing faults, and calls SystemInit
|
/Zephyr-latest/doc/project/ |
D | issues.rst | 24 To identify the commit causing the regression, several methods could be used,
|
/Zephyr-latest/dts/bindings/dma/ |
D | xilinx,axi-dma-base.yaml | 45 In this case, the python device tree script fails to assign ordinals, causing build failure.
|
/Zephyr-latest/subsys/demand_paging/eviction/ |
D | Kconfig | 38 and causing a fault when actually used, using such event to reorder
|
/Zephyr-latest/subsys/logging/ |
D | CMakeLists.txt | 58 # as this is causing CI failures. Actual root-cause is TBD.
|
/Zephyr-latest/arch/riscv/core/ |
D | irq_manage.c | 42 LOG_ERR("PLIC interrupt line causing the IRQ: %d (%p)", save_irq, save_dev); in z_irq_spurious()
|
/Zephyr-latest/soc/microchip/mec/common/reg/ |
D | mec_wdt.h | 38 * Kick WDT causing it to reload from LOAD register
|
/Zephyr-latest/boards/st/b_u585i_iot02a/ |
D | b_u585i_iot02a.dts | 36 /* The ATTR_MPU_EXTMEM attribut causing a MPU FAULT */
|
/Zephyr-latest/subsys/fs/ |
D | Kconfig | 34 disabled if the include paths for FS are causing aliasing
|
/Zephyr-latest/modules/lvgl/ |
D | Kconfig | 64 disabled if the include paths for LVGL are causing aliasing
|
/Zephyr-latest/soc/silabs/silabs_sim3/sim3u/ |
D | soc.c | 24 /* After a device reset, all crossbars enter a disabled default reset state, causing all in gpio_init()
|
1234