/Zephyr-latest/drivers/hwinfo/ |
D | hwinfo_mcux_src.c | 18 int z_impl_hwinfo_get_reset_cause(uint32_t *cause) in z_impl_hwinfo_get_reset_cause() argument 95 *cause = flags; in z_impl_hwinfo_get_reset_cause()
|
D | hwinfo_weak_impl.c | 19 int __weak z_impl_hwinfo_get_reset_cause(uint32_t *cause) in z_impl_hwinfo_get_reset_cause() argument
|
D | hwinfo_gecko.c | 35 int z_impl_hwinfo_get_reset_cause(uint32_t *cause) in z_impl_hwinfo_get_reset_cause() argument 152 *cause = flags; in z_impl_hwinfo_get_reset_cause()
|
D | hwinfo_nrf.c | 67 int z_impl_hwinfo_get_reset_cause(uint32_t *cause) in z_impl_hwinfo_get_reset_cause() argument 162 *cause = flags; in z_impl_hwinfo_get_reset_cause()
|
D | hwinfo_stm32.c | 67 int z_impl_hwinfo_get_reset_cause(uint32_t *cause) in z_impl_hwinfo_get_reset_cause() argument 159 *cause = flags; in z_impl_hwinfo_get_reset_cause()
|
/Zephyr-latest/include/zephyr/arch/mips/ |
D | exception.h | 50 unsigned long cause; member
|
/Zephyr-latest/drivers/watchdog/ |
D | wdt_xilinx_axi.c | 215 int z_impl_hwinfo_get_reset_cause(uint32_t *cause) in z_impl_hwinfo_get_reset_cause() argument 224 *cause = RESET_WATCHDOG; in z_impl_hwinfo_get_reset_cause() 226 *cause = 0; in z_impl_hwinfo_get_reset_cause()
|
/Zephyr-latest/soc/nordic/nrf52/ |
D | CMakeLists.txt | 13 …UND disabled with SPIS, SPIM, TWIM or PWM enabled. This will occasionally cause the first byte tra…
|
/Zephyr-latest/doc/hardware/peripherals/sensor/ |
D | triggers.rst | 7 generated events. Typically sensors allow setting up these events to cause
|
/Zephyr-latest/drivers/wifi/nrf_wifi/ |
D | CMakeLists.txt | 66 # These are XIP related anomalies and aren't applicable for nRF7002 and cause 70 # nRF70 QSPI doesn't use 192MHz clock and most samples use 128MHz, this can cause anomaly 159
|
/Zephyr-latest/samples/boards/google/twinkie_v2/pda/ |
D | README.rst | 25 usbc connection will cause the LED to turn blue. The LED will turn green instead
|
/Zephyr-latest/soc/native/inf_clock/ |
D | Kconfig.soc | 10 infinite loop in the code which does not sleep the CPU will cause the process
|
/Zephyr-latest/arch/mips/core/offsets/ |
D | offsets.c | 50 GEN_OFFSET_STRUCT(arch_esf, cause);
|
/Zephyr-latest/arch/nios2/ |
D | Kconfig | 59 the cause code for an exception will be supplemented by a string 60 describing what that cause code means.
|
/Zephyr-latest/drivers/serial/ |
D | Kconfig.altera | 23 Enabling this will cause the transmitter to wait for rising edge of CTS before sending.
|
/Zephyr-latest/boards/phytec/phyboard_pollux/ |
D | phyboard_pollux_mimx8ml8_m7.dts | 27 * BSP-Linux standard output. Can cause problems if used with standard bsp
|
/Zephyr-latest/tests/benchmarks/posix/threads/ |
D | Kconfig | 21 cause a crash.
|
/Zephyr-latest/cmake/compiler/xt-clang/ |
D | compiler_flags.cmake | 28 # Clear the related flag(s) here so it won't cause issues.
|
/Zephyr-latest/arch/riscv/core/ |
D | fatal.c | 55 const char *z_riscv_mcause_str(unsigned long cause) in z_riscv_mcause_str() argument 77 return mcause_str[MIN(cause, ARRAY_SIZE(mcause_str) - 1)]; in z_riscv_mcause_str()
|
/Zephyr-latest/cmake/modules/ |
D | python.cmake | 25 # cause just using find_program directly could result in a python2.7 as python,
|
/Zephyr-latest/subsys/logging/ |
D | CMakeLists.txt | 58 # as this is causing CI failures. Actual root-cause is TBD.
|
/Zephyr-latest/doc/develop/getting_started/ |
D | installation_win.rst | 17 Windows 10 version 1803 has an issue that will cause CMake to not work
|
/Zephyr-latest/subsys/pm/policy/ |
D | Kconfig | 30 that when the system transition to them, cause power loss in the device.
|
/Zephyr-latest/subsys/usb/device/class/dfu/ |
D | Kconfig | 62 Downloading the wrong image will cause a bricked device.
|
/Zephyr-latest/boards/shields/adafruit_neopixel_grid_bff/doc/ |
D | index.rst | 53 brightness. Having all of the LEDs on at once can cause the PCB to overheat
|