Searched refs:often (Results 51 – 75 of 78) sorted by relevance
1234
| /Zephyr-latest/doc/develop/ |
| D | beyond-GSG.rst | 354 and often is, a microprocessor running on its own dedicated hardware
|
| D | modules.rst | 57 West projects are often also modules, but not always. There are west projects
|
| /Zephyr-latest/subsys/debug/ |
| D | Kconfig | 457 Specifies how often CPU load shall be logged. 0 means that there is no logging.
|
| /Zephyr-latest/doc/project/ |
| D | dev_env_and_tools.rst | 246 Issues and PRs often have multiple labels assigned,
|
| /Zephyr-latest/doc/kernel/services/data_passing/ |
| D | mailboxes.rst | 56 receives the message data. An array or structure variable can often be used for
|
| /Zephyr-latest/doc/build/dts/ |
| D | howtos.rst | 59 When writing Zephyr applications, you'll often want to get a driver-level
|
| /Zephyr-latest/doc/develop/flash_debug/ |
| D | probes.rst | 66 an onboard debug probe often also have an SWD or JTAG header to enable the use
|
| /Zephyr-latest/doc/develop/application/ |
| D | index.rst | 754 The following variables will often need to be exported to the
918 is often significantly faster than building it the first time.
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | arch.rst | 35 * **Device drivers**: most often, the system clock timer and the interrupt
102 depends on the exception, but most often the core kernel itself is responsible
|
| /Zephyr-latest/doc/services/storage/zms/ |
| D | zms.rst | 159 It is not recommended for applications to use this function often, as it is time-consuming and
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | lwm2m.rst | 680 In LwM2M engine, there are three Kconfig options and one runtime value that configures how often the
|
| /Zephyr-latest/doc/services/tracing/ |
| D | index.rst | 260 it is often sufficient with a much smaller buffer, e.g. 1 KB or less.
|
| /Zephyr-latest/doc/kernel/services/threads/ |
| D | workqueue.rst | 412 in the work thread. More often external synchronization is required to avoid
|
| /Zephyr-latest/subsys/bluetooth/mesh/ |
| D | Kconfig | 1849 int "How often the sequence number gets updated in storage"
1854 This value defines how often the local sequence number gets
|
| /Zephyr-latest/ |
| D | CMakeLists.txt | 443 # W=1 - warnings that may be relevant and does not occur too often
444 # W=2 - warnings that occur quite often but may still be relevant
|
| /Zephyr-latest/doc/build/sysbuild/ |
| D | index.rst | 639 When integrating multiple applications with each other, then it is often
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-1.10.rst | 405 * :github:`4353` - VM-VM qemu networking example crashes often
|
| D | release-notes-3.6.rst | 1103 very helpful in diagnosing issues when using Picolibc as those are often caused by enabling TLS
|
| D | release-notes-2.6.rst | 1273 * :github:`35046` - Tracing shows k_busy_wait() being executed very often on nRF platforms
|
| D | release-notes-1.14.rst | 1153 * :github:`15183` - BLE HID sample often asserts on Windows 10 reconnection
|
| /Zephyr-latest/subsys/bluetooth/host/ |
| D | Kconfig | 516 This option defines how often resolvable private address is rotated.
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/audio/ |
| D | bluetooth-le-audio-arch.rst | 1185 The choice of what the return type of the callbacks often depend on the specifications,
|
| /Zephyr-latest/doc/security/ |
| D | vulnerabilities.rst | 7 fixed in each release. It will also often have more details than is
|
| /Zephyr-latest/doc/develop/test/ |
| D | twister.rst | 433 This option is often used to test drivers and the fact that they are correctly
|
| /Zephyr-latest/doc/ |
| D | zephyr.doxyfile.in | 488 # an expensive process and often the same symbol appears multiple times in the
|
1234
