Home
last modified time | relevance | path

Searched full:states (Results 1 – 25 of 477) sorted by relevance

12345678910>>...20

/Zephyr-latest/drivers/pinctrl/
Dcommon.c12 *state = &config->states[0]; in pinctrl_lookup_state()
13 while (*state < &config->states[config->state_cnt]) { in pinctrl_lookup_state()
26 const struct pinctrl_state *states, in pinctrl_update_states() argument
31 /* check we are inserting same number of states */ in pinctrl_update_states()
36 /* check we have the same states */ in pinctrl_update_states()
39 if (states[i].id == config->states[j].id) { in pinctrl_update_states()
50 /* replace current states */ in pinctrl_update_states()
51 config->states = states; in pinctrl_update_states()
/Zephyr-latest/subsys/net/lib/lwm2m/
Dlwm2m_rw_cbor.c69 ZCBOR_STATE_E(states, 0, CPKT_BUF_W_PTR(out->out_cpkt), CPKT_BUF_W_SIZE(out->out_cpkt), 1); in put_time()
72 ret = zcbor_tag_put(states, ZCBOR_TAG_TIME_TSTR); in put_time()
79 tag_sz = CPKT_CBOR_W_SZ(states[0].payload, out->out_cpkt); in put_time()
83 ret = zcbor_tstr_put_term(states, time_str, sizeof(time_str)); in put_time()
89 str_sz = CPKT_CBOR_W_SZ(states[0].payload, out->out_cpkt); in put_time()
102 ZCBOR_STATE_E(states, 0, CPKT_BUF_W_PTR(out->out_cpkt), CPKT_BUF_W_SIZE(out->out_cpkt), 1); in put_s64()
104 ret = zcbor_int64_encode(states, &value); in put_s64()
107 payload_len = CPKT_CBOR_W_SZ(states[0].payload, out->out_cpkt); in put_s64()
122 ZCBOR_STATE_E(states, 0, CPKT_BUF_W_PTR(out->out_cpkt), CPKT_BUF_W_SIZE(out->out_cpkt), 1); in put_s32()
124 ret = zcbor_int32_encode(states, &value); in put_s32()
[all …]
/Zephyr-latest/include/zephyr/pm/
Dstate.h18 * @brief System Power Management States
19 * @defgroup subsys_pm_states States
41 * requirements for the devices, leaving them at the states where
52 * peripherals into low-power states. No operating state is lost (ie.
62 * In addition to putting peripherals into low-power states all
107 /** Number of power management states (internal use) */
118 * Some platforms have multiple states that map to
123 * power-states {
204 * @note Only enabled states are initialized.
217 * @note Only enabled states are initialized.
[all …]
/Zephyr-latest/subsys/pm/
Dstate.c29 * @brief Check CPU power states consistency
31 * All states should have a minimum residency >= than the exit latency.
39 /* Check that all power states are consistent */
49 /** CPU power states information for each CPU */
54 /** Number of states for each CPU */
59 uint8_t pm_state_cpu_get_all(uint8_t cpu, const struct pm_state_info **states) in pm_state_cpu_get_all() argument
65 *states = cpus_states[cpu]; in pm_state_cpu_get_all()
/Zephyr-latest/tests/subsys/pm/power_states_api/src/
Dmain.c19 static enum pm_state states[] = {PM_STATE_SUSPEND_TO_IDLE, enum
56 zassert_true(ARRAY_SIZE(states) == dts_states_len, in ZTEST()
57 "Invalid number of pm states"); in ZTEST()
60 zassert_true(memcmp(states, dts_states, ARRAY_SIZE(dts_states)) == 0, in ZTEST()
61 "Invalid pm-states array"); in ZTEST()
64 "Invalid pm-states array"); in ZTEST()
71 "Invalid number of pm states"); in ZTEST()
/Zephyr-latest/doc/services/pm/
Dsystem.rst11 power management subsystem to put an idle system into one of the supported power states.
72 Power States
75 The power management subsystem defines a set of states described by the
78 The set of power states is defined by :c:enum:`pm_state`. In general, lower power states
91 The policy manager can only choose between states that have been defined for the platform.
92 Other constraints placed upon the decision may include locks disallowing certain power states,
95 More details on the states definition can be found in the
125 .. _pm-policy-power-states:
127 Policy and Power States
132 into certain power states. This can be used by devices when executing tasks in
Ddevice.rst36 put devices into low-power states (suspend) when they are not in
64 Management subsystem is able to change power states quickly because it
91 an example of a target with two low power states with only one triggering device power
98 power-states {
152 Device Power Management States
155 The power management subsystem defines device states in
156 :c:enum:`pm_device_state`. This method is used to track power states of
165 :caption: Device actions x states
190 As mentioned above, device drivers do not directly change between these states.
299 can cause device hardware to lose some states. Suspending a device which is in
[all …]
/Zephyr-latest/doc/hardware/peripherals/sensor/
Dpower_management.rst4 Power management of sensors is often a non-trivial task as sensors may have multiple power states
7 low power states sensors may lose their state, turning off even the digital logic portion of the de…
10 channel states are mutable using :ref:`sensor-attribute`. While total device suspending and resume
14 Most likely the API sensors should use for their fully suspended/resume power states is
/Zephyr-latest/dts/bindings/pinctrl/
Dpinctrl-device.yaml6 controller states. The maximum number of supported states is 5 (pinctrl-0 ...
42 Names for the provided states. The number of names needs to match the
43 number of states.
/Zephyr-latest/drivers/regulator/
Dregulator_gpio.c22 const int32_t *states; member
104 *volt_uv = cfg->states[idx * 2]; in regulator_gpio_list_voltage()
118 if (!IN_RANGE(cfg->states[state_idx * 2], min_uv, max_uv) || in regulator_gpio_set_voltage()
119 cfg->states[state_idx * 2] >= best_voltage) { in regulator_gpio_set_voltage()
123 best_voltage = cfg->states[state_idx * 2]; in regulator_gpio_set_voltage()
124 best_state = cfg->states[state_idx * 2 + 1]; in regulator_gpio_set_voltage()
128 LOG_ERR("%s: can't find voltage is states", dev->name); in regulator_gpio_set_voltage()
216 BUILD_ASSERT(!(DT_INST_PROP_LEN(inst, states) & 0x1), \
217 "Number of regulator states should be even"); \
222 .states = ((const int[])DT_INST_PROP(inst, states)), \
[all …]
/Zephyr-latest/tests/drivers/pinctrl/api/src/
Dmain.c30 * Device 0 is also used to verify that certain states are skipped
46 scfg = &pcfg0->states[0]; in ZTEST()
57 * Device 1 is also used to verify that custom states can be defined.
70 scfg = &pcfg1->states[0]; in ZTEST()
80 scfg = &pcfg1->states[1]; in ZTEST()
101 zassert_equal_ptr(scfg, &pcfg0->states[0], NULL); in ZTEST()
114 zassert_equal(pcfg0->states[0].pins, pinctrl_configure_pins_fake.arg0_val); in ZTEST()
115 zassert_equal(pcfg0->states[0].pin_cnt, pinctrl_configure_pins_fake.arg1_val); in ZTEST()
128 /** Test device 0 alternative states. */
133 /** Test device 0 invalid alternative states. */
[all …]
/Zephyr-latest/include/zephyr/drivers/
Dpinctrl.h36 * @name Pin control states
46 /** This and higher values refer to custom private states. */
71 const struct pinctrl_state *states; member
106 * @brief Obtain the variable name storing pinctrl states for the given DT node
167 * @brief Define all the states for the given node identifier.
187 .states = Z_PINCTRL_STATES_NAME(node_id), \
193 .states = Z_PINCTRL_STATES_NAME(node_id), \
236 * also defined and initialized. Note that states marked to be skipped will not
423 * @brief Update states with a new set.
425 * @note In order to guarantee device drivers correct operation the same states
[all …]
/Zephyr-latest/doc/connectivity/bluetooth/shell/audio/
Dbap.rst75 :header: "Command", "Depends", "Allowed States", "Next States"
306 :header: "Depends", "Allowed States", "Next States"
322 :header: "Depends", "Allowed States", "Next States"
497 :header: "Depends", "Allowed States", "Next States"
528 :header: "Depends", "Allowed States", "Next States"
543 :header: "Depends", "Allowed States", "Next States"
561 :header: "Depends", "Allowed States", "Next States"
576 :header: "Depends", "Allowed States", "Next States"
593 :header: "Depends", "Allowed States", "Next States"
609 :header: "Depends", "Allowed States", "Next States"
[all …]
/Zephyr-latest/subsys/net/l2/ethernet/gptp/
Dgptp_state.h22 /* PDelayRequest states. */
33 /* Path Delay Response states. */
41 /* SyncReceive states. */
48 /* SyncSend states. */
55 /* PortSyncSyncReceive states. */
61 /* PortSyncSyncSend states. */
69 /* SiteSyncSyncReceive states. */
75 /* ClockSlaveSync states. */
81 /* PortAnnounceReceive states. */
87 /* PortAnnounceInformation states. */
[all …]
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Dsar_cfg_srv.rst13 The model defines a set of states and messages for the SAR configuration.
15 The SAR Configuration Server model defines two states, SAR Transmitter state and SAR Receiver state.
16 For more information about the two states, see :ref:`bt_mesh_sar_cfg_states`.
Dsar_cfg_cli.rst14 The model can send messages to query or change the states supported by the SAR Configuration Server
27 For more information about the two states, see :ref:`bt_mesh_sar_cfg_states`.
29 An element can send any SAR Configuration Client message at any time to query or change the states
/Zephyr-latest/dts/bindings/regulator/
Dregulator-gpio.yaml18 states = <3300000 2>, <2700000 1>, <1800000 0>;
51 states:
55 GPIO configurations to achieve them. If there are no states in the
56 "states" array, use a fixed regulator instead. First value in an array
/Zephyr-latest/tests/subsys/pm/policy_api/
Dapp.overlay11 cpu-power-states = <&state2>;
15 power-states {
43 cpu-power-states = <&state0 &state1>;
/Zephyr-latest/tests/subsys/pm/power_states_api/boards/
Dnative_sim.overlay10 cpu-power-states = <&state0 &state1 &state2 &state3>;
13 power-states {
46 zephyr,disabling-power-states = <&state1 &state2>;
/Zephyr-latest/lib/smf/
DKconfig12 bool "States to have 1 or more ancestors"
18 bool "Support initial transitions for ancestor states"
/Zephyr-latest/tests/subsys/pm/device_wakeup_api/boards/
Dnative_sim.overlay8 power-states {
24 cpu-power-states = <&state0>;
/Zephyr-latest/doc/hardware/pinctrl/
Dindex.rst71 when suspending the device. Such requirements are modeled using **states**, a
73 driver owns a set of states. Each state has a unique name and contains a full
75 means that states are independent of each other, so they do not need to be
79 .. table:: Example pin configuration encoded using the states model
96 Standard states
99 The name assigned to pin control states or the number of them is up to the
104 details the standardized states and its purpose.
121 Note that other standard states could be introduced in the future.
123 Custom states
126 Some device drivers may require using custom states beyond the standard ones. To
[all …]
/Zephyr-latest/dts/bindings/cpu/
Dcpu.yaml12 cpu-power-states:
14 description: List of power management states supported by this cpu
/Zephyr-latest/include/zephyr/drivers/clock_control/
Darm_clock_control.h24 /* CPU States */
34 /* Clock can be configured for 3 states: Active, Sleep, Deep Sleep */
/Zephyr-latest/dts/bindings/base/
Dpm.yaml25 zephyr,disabling-power-states:
28 List of power states that will disable this device power.

12345678910>>...20