Searched full:followed (Results 1 – 25 of 166) sorted by relevance
1234567
/Zephyr-latest/tests/arch/riscv/fatal/src/ |
D | main.c | 14 * followed by zeros to pad to 32 bits, in main() 15 * followed by FF00, followed by hex number of the register, in main()
|
/Zephyr-latest/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-latest/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-latest/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-latest/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-latest/include/zephyr/logging/ |
D | log.h | 42 * followed by as many values as specifiers. 53 * followed by as many values as specifiers. 63 * followed by as many values as specifiers. 73 * followed by as many values as specifiers. 84 * followed by as many values as specifiers. 102 * followed by as many values as specifiers. 112 * followed by as many values as specifiers. 126 * followed by as many values as specifiers. 142 * specifier, followed by as many values as specifiers. 157 * followed by as many values as specifiers. [all …]
|
/Zephyr-latest/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-latest/dts/bindings/arm/ |
D | nxp,mcux-xbar.yaml | 17 Crossbar input and output mappings. Input is followed by the output.
|
/Zephyr-latest/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-latest/include/zephyr/arch/arm64/ |
D | arm_mem.h | 11 * followed public definitions in include/kernel/mm.h.
|
/Zephyr-latest/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-latest/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-latest/cmake/modules/ |
D | Findarmclang.cmake | 23 # Compiler version is either terminated directly, or followed by space and extra build info.
|
/Zephyr-latest/include/zephyr/sensing/ |
D | sensing_sensor_types.h | 13 * Sensor types definition followed HID standard.
|
/Zephyr-latest/dts/bindings/dma/ |
D | xilinx,axi-dma-base.yaml | 18 description: TX IRQ number followed by RX IRQ number
|
/Zephyr-latest/include/zephyr/linker/ |
D | intlist.ld | 18 * defined, the total number of IRQ lines in the system, followed by
|
/Zephyr-latest/subsys/logging/backends/ |
D | Kconfig.fs | 47 The prefix is followed by the number of log file.
|
/Zephyr-latest/samples/subsys/console/getline/ |
D | README.rst | 39 Now start pressing keys on a keyboard, followed by Enter. The input line
|
/Zephyr-latest/ |
D | CONTRIBUTING.rst | 20 * The Developer Certificate of Origin (DCO) process is followed to
|
/Zephyr-latest/drivers/sensor/renesas/hs300x/ |
D | hs300x.c | 71 * from its sleep state. An MR command should consist of the 7-bit address followed in hs300x_sample_fetch() 74 * should be followed by a dummy byte (zero value). in hs300x_sample_fetch()
|
/Zephyr-latest/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-latest/doc/services/tfm/ |
D | testsuites.rst | 27 being followed by the secure application, TF-M being an implementation of
|
/Zephyr-latest/include/zephyr/shell/ |
D | shell_dummy.h | 51 * The returned data is always followed by a nul character at position *sizep
|
/Zephyr-latest/include/zephyr/drivers/sensor/ |
D | icm42670.h | 35 * also the AAF cannot be bypassed. The AAF is followed by a 1st Order Low Pass
|
1234567