Searched full:would (Results 1 – 25 of 641) sorted by relevance
12345678910>>...26
| /Zephyr-Core-3.4.0/tests/kernel/device/ |
| D | CMakeLists.txt | 12 # optimizations. There would be multiple copies of the same string,
13 # and the code pathing doing pointer comparison would not be tested
15 # the pointer comparison would be exercised.
|
| /Zephyr-Core-3.4.0/tests/kernel/pipe/pipe_api/src/ |
| D | test_pipe_avail.c | 78 * would read: a b c d
81 * would overwrite: e f g h
117 * would read: e f g h
120 * would overwrite: a b c d
160 * would read:
163 * would overwrite: e f g h a b c d
203 * would read: e f g h a b c d
206 * would overwrite:
|
| /Zephyr-Core-3.4.0/doc/build/dts/ |
| D | bindings-intro.rst | 56 For example, the build system would use the above binding to check that the
65 For another example, the following node would cause a build error, because it
90 The ``baz-device`` node would get matched to a binding with a ``compatible:
109 above example binding would be named :file:`foo-company,bar-device.yaml` by
135 :file:`my-app/dts/bindings/serial/my-company,my-serial-port.yaml` would be
136 found, but :file:`my-app/my-company,my-serial-port.yaml` would be ignored.
|
| /Zephyr-Core-3.4.0/doc/connectivity/networking/api/ |
| D | ethernet_mgmt.rst | 19 Typically the ``carrier OFF`` event would be generated by the Ethernet
21 The ``carrier ON`` event would be generated if the Ethernet device driver
|
| /Zephyr-Core-3.4.0/lib/cpp/abi/ |
| D | cpp_dtors.c | 20 * would override its host libC counterpart. And this would both disable the atexit()
|
| /Zephyr-Core-3.4.0/include/zephyr/linker/ |
| D | thread-local-storage.ld | 17 * sections or else they would be considered
18 * thread-local variables, and the code would use
|
| /Zephyr-Core-3.4.0/dts/bindings/gpio/ |
| D | nuvoton,npcx-gpio.yaml | 27 For example the WUI mapping on NPCX7 GPIO8 would be
38 For example the LVOL mapping on NPCX7 GPIOC would be
|
| /Zephyr-Core-3.4.0/dts/bindings/spi/ |
| D | infineon,xmc4xxx-spi.yaml | 63 The interrupt would map to SR1. From Table "DMA Request Source Selection", request_source
64 would need to be set to 10 and the dts entry would be:
|
| /Zephyr-Core-3.4.0/include/zephyr/drivers/flash/ |
| D | nrf_qspi_nor.h | 23 * things as that would make XIP to fail. Hence, the application should use
30 * idle actions that would make XIP to fail
|
| /Zephyr-Core-3.4.0/.github/workflows/ |
| D | stale_issue.yml | 16 would like to have the label removed otherwise this pull request will automatically be
20 would like to have the label removed otherwise this issue will automatically be closed in
|
| /Zephyr-Core-3.4.0/include/zephyr/mgmt/ec_host_cmd/ |
| D | simulator.h | 20 * @brief Install callback for when this device would sends data to host
27 * @param cb Callback that is called when device would send data to host.
|
| /Zephyr-Core-3.4.0/cmake/linker_script/common/ |
| D | thread-local-storage.cmake | 19 # sections or else they would be considered
20 # thread-local variables, and the code would use
|
| /Zephyr-Core-3.4.0/samples/boards/intel_adsp/code_relocation/ |
| D | linker_xtensa_intel_adsp_cavs.ld | 25 * script would also place some BSS section on SRAM0, which would break
53 * linker script would add them after DATA, thus breaking contiguousness.
|
| /Zephyr-Core-3.4.0/dts/bindings/serial/ |
| D | infineon,xmc4xxx-uart.yaml | 108 The interrupt would map to SR1. From Table "DMA Request Source Selection", request_source
109 would need to be set to 10 and the dts entry would be:
|
| /Zephyr-Core-3.4.0/tests/kernel/timer/timer_behavior/ |
| D | prj.conf | 6 # 115200 bauds would grab the printk lock and disable IRQs for more
|
| /Zephyr-Core-3.4.0/subsys/net/lib/mqtt/ |
| D | mqtt_decoder.c | 28 * @retval -EINVAL if the buffer would be exceeded during the read
54 * @retval -EINVAL if the buffer would be exceeded during the read
81 * @retval -EINVAL if the buffer would be exceeded during the read
124 * @retval -EINVAL if the buffer would be exceeded during the read
158 * @retval -EINVAL if the length decoding would use more that 4 bytes.
159 * @retval -EAGAIN if the buffer would be exceeded during the read.
|
| /Zephyr-Core-3.4.0/tests/benchmarks/latency_measure/boards/ |
| D | mec1501modular_assy6885.conf | 2 # The test would not finish otherwise as there is no external
|
| D | mec15xxevb_assy6853.conf | 2 # The test would not finish otherwise as there is no external
|
| /Zephyr-Core-3.4.0/drivers/flash/ |
| D | Kconfig.mcux | 91 This prevents faults when the data to write would be located on the
100 This prevents faults when the data to write would be located on the
|
| /Zephyr-Core-3.4.0/cmake/modules/ |
| D | FindLlvmLld.cmake | 31 # to limit which linker to use, or else we would be using
37 # as it would complain about it not being a generic linker,
|
| /Zephyr-Core-3.4.0/samples/boards/nrf/mesh/onoff-app/ |
| D | README.rst | 34 using one button for "on" and another for "off" would reduce the number
40 This sample has been tested on the Nordic nRF52840-PDK board, but would
58 would expect with an actual switch.
|
| /Zephyr-Core-3.4.0/tests/subsys/portability/cmsis_rtos_v1/src/ |
| D | thread_apis.c | 44 /* By now thread1 would have set thread_yield_check to 1 and would in thread2()
45 * have yielded the CPU. Incrementing it over here would essentially in thread2()
|
| /Zephyr-Core-3.4.0/tests/kernel/mem_protect/userspace/boards/ |
| D | mimxrt595_evk_cm33.overlay | 10 * otherwise would be taken up for the SRAM1 USB region.
|
| D | mimxrt685_evk_cm33.overlay | 10 * otherwise would be taken up for the SRAM1 USB region.
|
| /Zephyr-Core-3.4.0/kernel/include/ |
| D | kernel_internal.h | 257 * This function would notify exit from kernel idling if a corresponding
261 * This function would be called from the ISR context of the event
264 * any operations before the kernel would switch tasks or processes nested
265 * interrupts. This is required for cpu low power states that would require
267 * those cases, the ISR would be invoked immediately after the event wakes up
|
12345678910>>...26
