Searched full:despite (Results 1 – 25 of 32) sorted by relevance
12
/Zephyr-latest/arch/arc/core/ |
D | cpu_idle.S | 46 /* z_arc_cpu_sleep_mode is 32 bit despite of platform bittnes */ 71 /* z_arc_cpu_sleep_mode is 32 bit despite of platform bittnes */
|
D | switch.S | 66 /* _thread_arch.relinquish_cause is 32 bit despite of platform bittnes */
|
D | regular_irq.S | 258 * _thread_arch.relinquish_cause is 32 bit despite of platform bittnes
|
/Zephyr-latest/drivers/spi/ |
D | Kconfig.nrfx | 72 bool "Allow enabling the SPIM driver despite PAN 58" 74 Allow enabling the nRF SPI Master with EasyDMA, despite
|
D | spi_emul.c | 42 * support chip selects, despite there being a chipsel field. It cannot be
|
/Zephyr-latest/subsys/usb/device/class/dfu/ |
D | Kconfig | 47 the executable image is always decrypted despite the image
|
/Zephyr-latest/dts/bindings/led_strip/ |
D | ws2812.yaml | 46 This default is good for the WS2812 controllers. Note that despite the
|
/Zephyr-latest/arch/arc/include/ |
D | swap_macros.h | 319 /* _cpu_t.nested is 32 bit despite of platform bittnes */ 323 /* z_kernel.nested is 32 bit despite of platform bittnes */ 345 /* _cpu_t.nested is 32 bit despite of platform bittnes */ 349 /* z_kernel.nested is 32 bit despite of platform bittnes */ 469 /* _thread_arch.relinquish_cause is 32 bit despite of platform bittnes */
|
/Zephyr-latest/dts/bindings/gpio/ |
D | nxp,s32-gpio.yaml | 35 despite being named WKPU, the flag is not meant to configure GPIOs as wake-up
|
/Zephyr-latest/tests/bluetooth/common/testlib/src/ |
D | security.c | 34 * ensures variables have the expected values despite non-atomic in security_changed()
|
/Zephyr-latest/soc/intel/intel_adsp/ace/ |
D | power_down.S | 81 * simplicity and directness, despite the potential performance benefits
|
/Zephyr-latest/doc/develop/test/ |
D | twister_statuses.rst | 49 despite them being called "Suites" there.
|
/Zephyr-latest/doc/build/kconfig/ |
D | menuconfig.rst | 71 despite being part of the standard library.
|
/Zephyr-latest/subsys/usb/device_next/ |
D | usbd_core.c | 74 LOG_ERR("Failed to get cfg_nd, despite configured state"); in usbd_class_bcast_event()
|
/Zephyr-latest/modules/hostap/ |
D | Kconfig | 77 # hostap debug is very verbose and despite large log buffer sizes
|
/Zephyr-latest/include/zephyr/drivers/firmware/scmi/ |
D | util.h | 80 * Despite this, users should opt for this macro instead of the TX-specific
|
/Zephyr-latest/tests/arch/arm/arm_interrupt/ |
D | README.txt | 22 The second test verifies that threads in user mode, despite being able to call
|
/Zephyr-latest/arch/riscv/core/ |
D | fpu.c | 211 "called despite FPU being accessible"); in z_riscv_fpu_trap()
|
/Zephyr-latest/drivers/timer/ |
D | hpet.c | 297 * on the other CPU, despite the HPET being in hpet_isr()
|
/Zephyr-latest/cmake/modules/ |
D | dts.cmake | 354 # of images having a newer modification time than the sysbuild build.ninja file, despite the
|
/Zephyr-latest/tests/arch/riscv/fpu_sharing/src/ |
D | main.c | 230 * assigned to it. This means we should still own it despite not in thread2_entry()
|
/Zephyr-latest/subsys/mgmt/ec_host_cmd/backends/ |
D | ec_host_cmd_backend_spi_stm32.c | 543 * before next transaction starts despite its setting is not changed.", in prepare_rx()
|
/Zephyr-latest/doc/releases/ |
D | release-notes-3.2.rst | 933 are different despite the similar terms -- was a frequent source of user 1725 - :github:`48505` - BLE stack can get stuck in connected state despite connection failure 1894 * :github:`50118` - Twister: ``--coverage-formats`` Does not work despite ``--coverage`` added 2160 * :github:`48198` - NPCX Tachometer driver compiled despite status = "disabled" 2451 * :github:`45774` - drivers: gpio: pca9555: Driver is writing to output port despite all pins been …
|
/Zephyr-latest/doc/contribute/ |
D | guidelines.rst | 598 If you want to override checkpatch verdict and push you branch despite reported
|
/Zephyr-latest/tests/lib/json/src/ |
D | main.c | 1201 zassert_equal(ret, 0, "Encoding failed despite large enough buffer"); in ZTEST()
|
12