Searched refs:executing (Results 1 – 25 of 87) sorted by relevance
1234
| /Zephyr-Core-3.7.0/lib/smf/ |
| D | smf.c | 106 ctx->executing = to_execute; in smf_execute_all_entry_actions()
119 ctx->executing = new_state; in smf_execute_all_entry_actions()
160 ctx->executing = tmp_state; in smf_execute_ancestor_run_actions()
235 ctx->executing = init_state; in smf_set_initial()
283 if (share_paren(ctx->executing, new_state)) { in smf_set_state()
286 } else if (share_paren(new_state, ctx->executing)) { in smf_set_state()
288 topmost = ctx->executing; in smf_set_state()
291 topmost = get_lca_of(ctx->executing, new_state); in smf_set_state()
304 if ((ctx->executing == new_state) && (new_state->exit)) { in smf_set_state()
316 if ((ctx->executing == new_state) && (new_state->entry)) { in smf_set_state()
[all …]
|
| /Zephyr-Core-3.7.0/include/zephyr/ |
| D | smf.h | 107 const struct smf_state *executing; member
|
| /Zephyr-Core-3.7.0/samples/net/sockets/tcp/ |
| D | README.rst | 13 Building, Running and executing TTCN-3 based Sanity Check for TCP
|
| /Zephyr-Core-3.7.0/doc/kernel/services/threads/ |
| D | system_threads.rst | 25 initialization or executing the application's :c:func:`main` function;
56 An application-supplied :c:func:`main` function begins executing once
|
| /Zephyr-Core-3.7.0/cmake/ |
| D | verify-toolchain.cmake | 22 # If executing in script mode and output format is specified, then silence
|
| /Zephyr-Core-3.7.0/subsys/net/lib/tls_credentials/ |
| D | Kconfig | 54 by executing a separate binary.
|
| /Zephyr-Core-3.7.0/boards/nordic/nrf54h20dk/doc/ |
| D | index.rst | 31 the PPR core on the nRF54H20 SoC executing from RAM.
33 the PPR core on the nRF54H20 SoC executing from MRAM.
|
| /Zephyr-Core-3.7.0/doc/ |
| D | glossary.rst | 84 A group of one or more :term:`CPU cores <CPU core>`, all executing the same image
91 A single processing unit, with its own Program Counter, executing program
115 executing on the processor.
191 (eXecute In Place) a method of executing programs directly from long
|
| /Zephyr-Core-3.7.0/subsys/input/ |
| D | Kconfig | 66 enough space for executing the registered callbacks.
|
| /Zephyr-Core-3.7.0/arch/arm/core/ |
| D | Kconfig | 227 Code executing in Secure state has access to both the Secure
230 Code executing in Non-Secure state may trigger Secure Faults,
232 Secure Faults may only be handled by code executing in Secure
251 Code executing in Non-Secure state has no access to Secure
|
| /Zephyr-Core-3.7.0/soc/andestech/ae350/ |
| D | Kconfig | 78 executing rate.
|
| /Zephyr-Core-3.7.0/kernel/ |
| D | Kconfig.smp | 74 priority than a currently executing thread on another CPU. Although
103 lower priority than all the threads currently executing on other CPUs.
|
| /Zephyr-Core-3.7.0/boards/lowrisc/opentitan_earlgrey/doc/ |
| D | index.rst | 70 the manifest header from simulated flash, and begin executing Zephyr from the
|
| /Zephyr-Core-3.7.0/soc/ite/ec/it8xxx2/ |
| D | Kconfig | 173 predictable than executing from Flash directly, and some code (such as code
182 has more reliable performance characteristics than executing directly from
|
| /Zephyr-Core-3.7.0/boards/infineon/cyw920829m2evk_02/doc/ |
| D | index.rst | 105 …ations. When doing a minimal installation, this can be done manually by executing the script ``ope…
139 Once the gdb console starts after executing the west debug command, you may now set breakpoints and…
|
| /Zephyr-Core-3.7.0/boards/native/doc/ |
| D | arch_soc.rst | 83 These limitations are due to the code executing natively in
155 keep the CPU executing and consuming power.
355 executing the boot of the embedded code (including the POSIX arch code).
367 At this point the last executing SW pthread will be blocked,
380 letting the last SW thread continue executing.
403 The Zephyr application sees the code executing as if the CPU were running at
|
| /Zephyr-Core-3.7.0/tests/arch/arm/arm_thread_swap/ |
| D | README.txt | 37 the mode in which a user thread is currently executing.
|
| /Zephyr-Core-3.7.0/samples/drivers/fpga/fpga_controller/ |
| D | README.rst | 66 After executing the sample, you can see at what address it is stored and its size in bytes.
|
| /Zephyr-Core-3.7.0/tests/drivers/watchdog/wdt_error_cases/ |
| D | README.txt | 36 As a result, executing this test suite on a target that doesn't
|
| /Zephyr-Core-3.7.0/doc/services/device_mgmt/ |
| D | mcumgr_handlers.rst | 43 itself and application code, e.g. to reference the command IDs for executing functions. An example
63 itself and application code, e.g. to reference the command IDs for executing functions. An example
|
| /Zephyr-Core-3.7.0/doc/develop/api/ |
| D | terminology.rst | 11 if executing the function reaches a reschedule point
13 if executing the function can cause the invoking thread to sleep
|
| /Zephyr-Core-3.7.0/doc/kernel/services/smp/ |
| D | smp.rst | 246 CPU0 and T1 not be pinned. If CPU0 is executing T2 and CPU1 executing T1,
247 then this set is is both valid and optimal. However, if CPU0 is executing
251 set, the resulting set of executing threads are expected to be close to a valid
261 must be done to compare the old thread against the threads executing on the
|
| /Zephyr-Core-3.7.0/doc/safety/ |
| D | safety_requirements.rst | 66 If there are duplicates in the PR, these need to be resolved by rebasing and re-executing
|
| /Zephyr-Core-3.7.0/doc/services/resource_management/ |
| D | index.rst | 63 Failures in executing a transition are recorded and inhibit further
|
| /Zephyr-Core-3.7.0/samples/net/dns_resolve/ |
| D | README.rst | 85 net-tools uses port 5353 to allow executing the daemon without
|
1234
