Searched refs:actions (Results 1 – 25 of 42) sorted by relevance
12
| /Zephyr-latest/doc/services/smf/ |
| D | index.rst | 20 Entry actions, another function implements the Run actions, and the last
21 function implements the Exit actions. The prototype for these functions is as
125 should be called. It can be called from the entry, run, or exit actions. The
133 entry and exit actions of the least common ancestor are not executed on
141 1. Executing the actions associated with the transition within the context
142 of the source state, rather than after the exit actions are performed.
145 3. Prohibiting transitions using :c:func:`smf_set_state` in exit actions.
335 /* Child states do not have entry or exit actions */
338 /* State S2 do not have entry or exit actions and no parent */
362 - Ancestor entry actions are executed before the sibling entry actions. For
[all …]
|
| /Zephyr-latest/samples/subsys/zbus/benchmark/ |
| D | Kconfig | 28 bool "Force a comparison with same actions"
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | lwm2m.rst | 640 - No actions needed
642 - No actions needed
644 - No actions needed.
647 - No actions needed.
650 - No actions needed.
653 - No actions needed
656 - No actions needed, client proceeds to idle state automatically. Cannot send or receive data.
661 - No actions needed.
668 - No actions needed, client will re-register once the disable period is over.
733 One imaginable scenario, where to use the shell, would be executing client side actions over UART
[all …]
|
| D | ptp.rst | 64 :header: Management_ID, Management_ID name, Allowed actions
|
| /Zephyr-latest/ |
| D | README.rst | 15 …roject-rtos/zephyr/actions/workflows/twister.yaml?query=branch%3Amain"><img src="https://github.co…
|
| D | CODE_OF_CONDUCT.md | 91 actions.
|
| /Zephyr-latest/scripts/west_commands/ |
| D | run_common.py | 757 actions = group._group_actions
758 if len(actions) == 1 and actions[0].dest == 'command':
763 formatter.add_arguments(actions)
|
| /Zephyr-latest/subsys/task_wdt/ |
| D | Kconfig | 53 this value to provide sufficient time for corrective actions in the
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | provisioning.rst | 129 actions are listed in :c:enum:`bt_mesh_input_action_t`.
131 actions are listed in :c:enum:`bt_mesh_output_action_t`.
134 methods in :c:struct:`bt_mesh_prov`, as well as enabling the supported actions
|
| /Zephyr-latest/drivers/pinctrl/ |
| D | Kconfig | 18 actions are device dependent or require access to device specific
|
| /Zephyr-latest/samples/subsys/smf/hsm_psicc2/ |
| D | README.rst | 36 For each state, the entry, run, and exit actions are logged to the console, as well as logging
|
| /Zephyr-latest/samples/bluetooth/extended_adv/ |
| D | README.rst | 21 This sample handles all actions in a separate thread, to promote good design
|
| /Zephyr-latest/doc/services/pm/ |
| D | device.rst | 159 to handle device actions(:c:enum:`pm_device_action`) which change device state.
165 :caption: Device actions x states
263 Power management actions can be triggered from shell commands for testing
289 suspend and resume actions and it's currently active, ``buttons`` supports
|
| D | power_domain.rst | 144 state. These notifications are sent as actions in the device PM action
|
| /Zephyr-latest/subsys/testsuite/ztest/ |
| D | Kconfig | 90 do actions in your test case, this option often enabled when doing
98 do actions in your test case, this option often enabled when doing
|
| /Zephyr-latest/doc/safety/ |
| D | safety_requirements.rst | 50 These requirements define the specific actions the feature shall be able to execute and the
|
| /Zephyr-latest/drivers/serial/ |
| D | Kconfig.nrfx_uart_instance | 80 because then device state is controlled by the PM actions.
|
| /Zephyr-latest/doc/develop/tools/ |
| D | stm32cubeide.rst | 42 However, more actions must still be done in order to configure it properly.
|
| /Zephyr-latest/tests/bsim/bluetooth/mesh/ |
| D | README.rst | 82 This includes ``PASS``/``FAIL`` macros and some common mesh actions, such as
|
| /Zephyr-latest/doc/services/zbus/ |
| D | index.rst | 26 messages. Additionally, besides other actions, threads can publish and observe channels. When a
58 The bus makes the publish, read, claim, finish, notify, and subscribe actions available over
201 The figure above illustrates the actions performed during the VDED execution when T1 publishes to
253 The figure below illustrates the actions performed during the VDED execution when T1 publishes to
317 The figure below illustrates the actions performed during the VDED execution when T1 publishes to
773 safely. When a channel is claimed, no actions are available to that channel. After finishing the
774 channel, all the actions are available again.
|
| /Zephyr-latest/doc/project/ |
| D | working_groups.rst | 81 actions to be taken, and next steps.
|
| /Zephyr-latest/boards/ti/cc1352p7_launchpad/doc/ |
| D | index.rst | 149 …For your convenience, we provide a `prebuilt binary <https://github.com/anobli/openocd/actions/run…
|
| /Zephyr-latest/subsys/net/lib/ptp/ |
| D | Kconfig | 42 timers, depending on received PTP messages or timeouts actions defined
|
| /Zephyr-latest/doc/connectivity/networking/conn_mgr/ |
| D | main.rst | 220 …onal :ref:`convenience automations <conn_mgr_control_automations>` for common connectivity actions.
411 There are a few actions related to connectivity that are (by default at least) performed automatica…
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | mcumgr_handlers.rst | 92 the code to listen for the event and take any required actions that are necessary or prevent
|
12
