Searched refs:post (Results 51 – 75 of 78) sorted by relevance
1234
| /Zephyr-latest/tests/benchmarks/thread_metric/ |
| D | thread_metric_readme.txt | 48 increment a counter and then post to a semaphore. After the
|
| /Zephyr-latest/boards/st/stm32h747i_disco/doc/ |
| D | index.rst | 135 `DISCO_H747I modifications for Ethernet`_ mbed blog post. The author of this
|
| /Zephyr-latest/ |
| D | CMakeLists.txt | 1143 # only initialized post-kernel.
1681 …# Note: The use of generator expressions allows downstream extensions to add/change the post build.
1983 #slidgen must be the first post-build command to be executed
2092 # database, add the generation to post build command to make sure
2117 # Add post_build_commands to post-process the final .elf file produced by
|
| /Zephyr-latest/cmake/linker/armlink/ |
| D | scatter_script.cmake | 5 # This function post process the region for easier use.
|
| /Zephyr-latest/arch/riscv/ |
| D | Kconfig | 294 to collect for post-mortem analysis and debug of issues.
|
| /Zephyr-latest/doc/contribute/ |
| D | contributor_expectations.rst | 188 - After 2 weeks of inactivity, post a message on the `#pr-help`_ channel on
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-1.9.rst | 197 * Convert post-processing host tools to python, this includes the following
|
| D | release-notes-3.5.rst | 2176 * Added API :c:macro:`ZBUS_CHAN_ADD_OBS` macro for adding post-definition static observers of a
2179 the system using ZBus, making post-definition channel observation rely on the stack instead of
|
| D | migration-guide-3.7.rst | 887 during a Coap Block-wise transfer. Any post write, validate or some firmware callbacks
|
| D | release-notes-2.6.rst | 1012 ``warnings_filter``. This extension removes the need of post-processing
1913 * :github:`32474` - pm: review post sleep wake up application notification scheduling
2050 * :github:`30325` - Stack overflow with http post when using civetweb
|
| D | release-notes-2.1.rst | 781 * :github:`19004` - problems in sanitycheck/CI infrastructure revealed by post-release change
|
| D | release-notes-2.5.rst | 685 * Added TagoIO IoT Cloud HTTP post sample.
1539 * :github:`29261` - boards: musca_b1: post build actions with TF-M might not be done in right order
|
| D | release-notes-3.3.rst | 3515 * :github:`50354` - ztest_new: _zassert_base : return without post processing
3709 * :github:`40868` - Add a pre and post initialization among CONFIG_APPLICATION_INIT_PRIORITY
|
| /Zephyr-latest/dts/arm/nxp/ |
| D | nxp_rt10xx.dtsi | 987 * The pre-div and post-div are one less than the actual divide-by amount.
|
| D | nxp_rt11xx.dtsi | 208 * post divider. The output frequency is calculated
|
| /Zephyr-latest/doc/_doxygen/ |
| D | doxygen-awesome.css | 1360 dl.warning, dl.attention, dl.note, dl.deprecated, dl.bug, dl.invariant, dl.pre, dl.post, dl.todo, d…
1431 dl.invariant, dl.pre, dl.post {
1437 dl.invariant dt, dl.pre dt, dl.post dt {
|
| /Zephyr-latest/doc/services/zbus/ |
| D | index.rst | 516 that a post-definition static observer. The command enables us to indicate an initialization
518 the post-definition static observers. There is no possibility to overwrite the message delivery
|
| /Zephyr-latest/doc/develop/test/ |
| D | ztest.rst | 406 - Why not pre-scan with CPP and then parse? or post scan the ELF file?
|
| /Zephyr-latest/subsys/net/lib/coap/ |
| D | coap.c | 1143 *method = resource->post; in method_from_code()
|
| /Zephyr-latest/doc/services/tracing/ |
| D | index.rst | 385 SystemView can also be used for post-mortem tracing, which can be enabled with
|
| /Zephyr-latest/doc/contribute/coding_guidelines/ |
| D | index.rst | 1215 - This `CAN in Automation Inclusive Language news post`_ has a list of general
1261 .. _CAN in Automation Inclusive Language news post: https://www.can-cia.org/news/archive/view/?tx_n…
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | syscalls.rst | 60 simply expands to 'static inline'. However to the post-build
|
| /Zephyr-latest/arch/ |
| D | Kconfig | 602 to collect for post-mortem analysis and debug of issues.
|
| /Zephyr-latest/doc/develop/ |
| D | modules.rst | 755 If a module ``foo`` want to provide a post CMake configure function, then the
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | shell.rst | 1087 all Target nodes, then post a message when the transfer is completed. Note that all Target
|
1234
