Searched refs:doing (Results 76 – 100 of 113) sorted by relevance
12345
| /Zephyr-latest/doc/build/dts/ |
| D | api-usage.rst | 59 :c:macro:`DT_INST()`, but be careful doing so. See below.
|
| /Zephyr-latest/doc/kernel/services/scheduling/ |
| D | index.rst | 376 i.e. not doing any real work, like in this example below.
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/audio/ |
| D | mcp.rst | 30 found by doing :samp:`mcc {<command>} help` or :samp:`mpl {<command>} help`.
|
| /Zephyr-latest/doc/services/pm/ |
| D | device.rst | 307 longer doing an operation and can be suspended, it should call
|
| /Zephyr-latest/doc/kernel/services/timing/ |
| D | clocks.rst | 303 timeout and loop, waiting for it to finish while doing some processing
|
| /Zephyr-latest/doc/project/ |
| D | dev_env_and_tools.rst | 70 Any change that is a fix to an issue that blocks developers from doing their
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | board_porting.rst | 736 To see what a ``west flash`` or ``west debug`` command is doing exactly, run it
873 of doing regex matches internally, then string revisions must be done using
|
| D | arch.rst | 435 for doing real work after initialization, i.e. it is sitting in a loop doing
|
| /Zephyr-latest/doc/releases/ |
| D | migration-guide-3.5.rst | 360 macro call has been removed as it was not doing anything useful.
|
| D | release-notes-1.14.rst | 51 * :github:`29386` - unexpected behavior when doing syscall with 7 or more arguments
1231 …` - Bluetooth: Mesh: Provisioning state doesn't always get properly re-initialized when doing reset
2192 * :github:`8746` - net_app DTLS Client net/pkt ERR log when doing handshake
|
| /Zephyr-latest/doc/kernel/services/smp/ |
| D | smp.rst | 116 involved in doing the per-CPU mask test requires that the list be
|
| /Zephyr-latest/doc/security/ |
| D | sensor-threat.rst | 336 placed in. There are numerous ways of doing this, and it is important
|
| D | security-overview.rst | 66 a MUST or SHOULD, or doing something the specification says MUST NOT or
|
| /Zephyr-latest/scripts/west_commands/completion/ |
| D | west-completion.fish | 120 # we don't want the command completion when doing `west help <cmd>`
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | lwm2m.rst | 708 This is then affecting the period of updates the client is doing.
|
| /Zephyr-latest/doc/build/sysbuild/ |
| D | index.rst | 750 (in some order) before doing the same for ``my_sample``, when building these
|
| /Zephyr-latest/ |
| D | CMakeLists.txt | 466 # but we cannot tell that to the linker yet as we are first only doing a
1429 # Essentially what we are doing here is extracting some information
|
| D | Kconfig.zephyr | 696 --print-memory-region to the linker when it is doing it's first
|
| /Zephyr-latest/doc/hardware/arch/ |
| D | arm_cortex_m.rst | 394 thread may also be context-switched-out while doing a system call; the system call will
|
| /Zephyr-latest/kernel/ |
| D | Kconfig | 24 doing.
|
| /Zephyr-latest/subsys/bluetooth/host/ |
| D | Kconfig | 211 instead of each subsystem doing it independently.
|
| /Zephyr-latest/doc/contribute/documentation/ |
| D | guidelines.rst | 917 there, and will tweak the text to note that doing so again is not necessary.
|
| /Zephyr-latest/doc/contribute/ |
| D | guidelines.rst | 46 contributor, such as when the contributor is doing work on behalf of a
|
| /Zephyr-latest/doc/ |
| D | zephyr.doxyfile.in | 737 # only one candidate or it is obvious which candidate to choose by doing a
2075 # Note: Only use a user-defined header if you know what you are doing!
2091 # doing!
|
| /Zephyr-latest/doc/develop/ |
| D | modules.rst | 159 if applicable, etc.), and the reason for the doing the update.
|
12345
