Searched full:followed (Results 1 – 25 of 136) sorted by relevance
123456
| /Zephyr-Core-3.5.0/modules/hal_nordic/nrfx/ |
| D | nrfx_log.h | 56 * @param ... printf-style format string, optionally followed by arguments
64 * @param ... printf-style format string, optionally followed by arguments
72 * @param ... printf-style format string, optionally followed by arguments
80 * @param ... printf-style format string, optionally followed by arguments
|
| /Zephyr-Core-3.5.0/tests/subsys/sd/sdmmc/ |
| D | README.txt | 19 * Read test: verify that single block reads work, followed by multiple
23 * Write test: verify that single block writes work, followed by multiple
|
| /Zephyr-Core-3.5.0/tests/subsys/sd/mmc/ |
| D | README.txt | 19 * Read test: verify that single block reads work, followed by multiple
23 * Write test: verify that single block writes work, followed by multiple
|
| /Zephyr-Core-3.5.0/doc/develop/api/ |
| D | design_guidelines.rst | 8 be followed when developing a new capability or interface.
14 configuration structure. The following policies should be followed when
25 and/or a message pointer followed by the message length.
80 practices should be followed.
|
| /Zephyr-Core-3.5.0/include/zephyr/logging/ |
| D | log.h | 40 * followed by as many values as specifiers.
51 * followed by as many values as specifiers.
61 * followed by as many values as specifiers.
71 * followed by as many values as specifiers.
82 * followed by as many values as specifiers.
92 * followed by as many values as specifiers.
106 * followed by as many values as specifiers.
122 * specifier, followed by as many values as specifiers.
137 * followed by as many values as specifiers.
152 * followed by as many values as specifiers.
|
| /Zephyr-Core-3.5.0/samples/userspace/shared_mem/ |
| D | README.rst | 35 followed by two series of repeating messages. The repeating messages
49 The PT thread sends a message followed by the encrypted version of the
|
| /Zephyr-Core-3.5.0/samples/drivers/ipm/ipm_ivshmem/ |
| D | README.rst | 77 To run both QEMU sides, repeat the west build command followed
91 followed by the destination peer-id, to get the peer-id destination
107 instance and use the command to send the IPM notification followed
|
| /Zephyr-Core-3.5.0/dts/bindings/arm/ |
| D | nxp,mcux-xbar.yaml | 17 Crossbar input and output mappings. Input is followed by the output.
|
| /Zephyr-Core-3.5.0/include/zephyr/arch/arm64/ |
| D | arm_mem.h | 11 * followed public definitions in include/sys/mem_manage.h.
|
| /Zephyr-Core-3.5.0/include/zephyr/sensing/ |
| D | sensing_sensor_types.h | 13 * Sensor types definition followed HID standard.
|
| /Zephyr-Core-3.5.0/lib/libc/newlib/ |
| D | CMakeLists.txt | 59 # libc will be followed by libgcc, which is finally followed by libc again.
|
| /Zephyr-Core-3.5.0/include/zephyr/devicetree/ |
| D | ordinals.h | 48 * @return a list of dependency ordinals, with each ordinal followed
65 * @return a list of dependency ordinals, with each ordinal followed
|
| /Zephyr-Core-3.5.0/dts/bindings/gpio/ |
| D | seeed-xiao-header.yaml | 16 has three power pins, followed by four inputs labeled 10 at the
|
| D | sparkfun-pro-micro-header.yaml | 14 has four power pins, followed by eight inputs, with a
|
| /Zephyr-Core-3.5.0/cmake/modules/ |
| D | Findarmclang.cmake | 23 # Compiler version is either terminated directly, or followed by space and extra build info.
|
| /Zephyr-Core-3.5.0/subsys/logging/backends/ |
| D | Kconfig.fs | 39 The prefix is followed by the number of log file.
|
| /Zephyr-Core-3.5.0/include/zephyr/linker/ |
| D | intlist.ld | 18 * defined, the total number of IRQ lines in the system, followed by
|
| /Zephyr-Core-3.5.0/tests/drivers/smbus/smbus_api/src/ |
| D | test_smbus_qemu.c | 91 * operations: write, which sets offset, followed by read, which in ZTEST_USER()
106 * to test Block Write followed by Block Read in ZTEST_USER()
|
| /Zephyr-Core-3.5.0/samples/subsys/console/getline/ |
| D | README.rst | 39 Now start pressing keys on a keyboard, followed by Enter. The input line
|
| /Zephyr-Core-3.5.0/ |
| D | CONTRIBUTING.rst | 20 * The Developer Certificate of Origin (DCO) process is followed to
|
| /Zephyr-Core-3.5.0/include/zephyr/shell/ |
| D | shell_dummy.h | 51 * The returned data is always followed by a nul character at position *sizep
|
| /Zephyr-Core-3.5.0/doc/services/tfm/ |
| D | testsuites.rst | 27 being followed by the secure application, TF-M being an implementation of
|
| /Zephyr-Core-3.5.0/drivers/i2c/ |
| D | i2c_bitbang.c | 274 * a START condition followed by 9 STOP conditions. in i2c_bitbang_recover_bus()
277 * issuing a START condition followed by 9 SCL clock pulses in i2c_bitbang_recover_bus()
292 /* Another start condition followed by a stop condition */ in i2c_bitbang_recover_bus()
|
| /Zephyr-Core-3.5.0/tests/lib/newlib/heap_listener/src/ |
| D | main.c | 43 * This test calls the malloc() and free() followed by malloc_trim() functions
|
| /Zephyr-Core-3.5.0/scripts/west_commands/zspdx/ |
| D | getincludes.py | 44 # lines we want will start with one or more periods, followed by
|
123456
