Home
last modified time | relevance | path

Searched full:would (Results 1 – 25 of 842) sorted by relevance

12345678910>>...34

/Zephyr-latest/tests/kernel/device/
DCMakeLists.txt12 # 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-latest/drivers/usb/common/nrf_usbd_common/
Dnrf_usbd_common.h36 * This number would be shared between IN and OUT endpoint.
140 * This error would also be returned when next_transfer function
292 * After calling this function USBD peripheral would be enabled.
293 * The USB LDO would be enabled.
294 * Enabled USBD peripheral would request HFCLK.
296 * program after enabling USBD driver HFINT would be used for the USBD peripheral.
302 * Interrupts and USB pins pull-up would stay disabled until @ref nrf_usbd_common_start
310 * After calling this function USBD peripheral would be disabled.
311 * No events would be detected or processed by the driver.
312 * Clock for the peripheral would be disconnected.
[all …]
/Zephyr-latest/tests/kernel/pipe/pipe_api/src/
Dtest_pipe_avail.c78 * 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-latest/doc/build/dts/
Dbindings-intro.rst56 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-latest/doc/connectivity/networking/api/
Dethernet_mgmt.rst19 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-latest/dts/bindings/sensor/
Dams,tsl2540.yaml25 Example: 1.2 would be 120000
34 Example: 1.2 would be 120000
/Zephyr-latest/scripts/native_simulator/common/src/include/
Dnsi_main.h19 * return to the caller what would have been passed to exit()
25 * @returns Code which would have been passed to exit()
/Zephyr-latest/lib/cpp/abi/
Dcpp_dtors.c20 * would override its host libC counterpart. And this would both disable the atexit()
/Zephyr-latest/doc/services/device_mgmt/
Dmcumgr_handlers.rst44 file would look similar to:
64 file would look similar to:
82 register the transport with MCUmgr so that commands will be sent to it. An example file would
104 to the functionality of the handler being implemented. An example file would look similar to:
114 source files if the Kconfig options are enabled. An example file would look similar to:
170 module directory, and would be placed at ``zephyr/module.yml``:
182 and would be placed at ``CMakeLists.txt``:
192 would be placed at ``Kconfig``:
/Zephyr-latest/dts/bindings/gpio/
Dnuvoton,npcx-gpio.yaml27 For example the WUI mapping on NPCX7 GPIO8 would be
38 For example the LVOL mapping on NPCX7 GPIOC would be
/Zephyr-latest/include/zephyr/drivers/flash/
Dnrf_qspi_nor.h23 * things as that would make XIP to fail. Hence, the application should use
30 * idle actions that would make XIP to fail
/Zephyr-latest/.github/workflows/
Dstale_issue.yml16 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-latest/dts/bindings/spi/
Dinfineon,xmc4xxx-spi.yaml63 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-latest/include/zephyr/linker/
Dthread-local-storage.ld17 * sections or else they would be considered
18 * thread-local variables, and the code would use
/Zephyr-latest/doc/build/flashing/
Dconfiguration.rst11 which would prevent multiple erase tasks running in a single ``west flash`` invocation, which
27 child, this then contains a map of commands as they would be provided to the flash runner e.g.
105 If the above was ran without the flashing configuration, the recovery process would be ran twice
106 and the device would be unbootable.
/Zephyr-latest/subsys/bindesc/
DKconfig.version36 3.4.0 would be represented as 0x30400
69 1.0.0 would be represented as 0x10000
/Zephyr-latest/cmake/linker_script/common/
Dthread-local-storage.cmake19 # sections or else they would be considered
20 # thread-local variables, and the code would use
/Zephyr-latest/dts/bindings/ipc/
Dnordic,nrf-ipct-common.yaml29 channel 4, then the array "unit" would be <2 NRF_DOMAIN_ID_RADIOCORE 4>
44 channel 4, then the array "unit" would be <2 NRF_DOMAIN_ID_RADIOCORE 4>
/Zephyr-latest/include/zephyr/mgmt/ec_host_cmd/
Dsimulator.h20 * @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-latest/tests/kernel/threads/thread_error_case/boards/
Dqemu_xtensa_dc233c_mmu.conf1 # For some weird reasons, enabling ICOUNT would crash QEMU
/Zephyr-latest/tests/posix/single_process/
Dprj.conf4 # Let's explicitly choose PICOLIBC, so it is used if supported even if it would not have been the
/Zephyr-latest/drivers/flash/
DKconfig.mcux103 This prevents faults when the data to write would be located on the
112 This prevents faults when the data to write would be located on the
/Zephyr-latest/tests/kernel/timer/timer_behavior/
Dprj.conf5 # 115200 bauds would grab the printk lock and disable IRQs for more
/Zephyr-latest/tests/benchmarks/latency_measure/boards/
Dmec1501modular_assy6885.conf2 # The test would not finish otherwise as there is no external
Dmec15xxevb_assy6853.conf2 # The test would not finish otherwise as there is no external

12345678910>>...34