/Zephyr-latest/subsys/net/lib/lwm2m/ |
D | lwm2m_rw_cbor.c | 69 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/drivers/pinctrl/ |
D | common.c | 12 *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 39 if (states[i].id == config->states[j].id) { in pinctrl_update_states() 51 config->states = states; in pinctrl_update_states()
|
/Zephyr-latest/drivers/regulator/ |
D | regulator_gpio.c | 22 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() 216 BUILD_ASSERT(!(DT_INST_PROP_LEN(inst, states) & 0x1), \ 222 .states = ((const int[])DT_INST_PROP(inst, states)), \ 223 .states_cnt = DT_INST_PROP_LEN(inst, states) / 2, \
|
/Zephyr-latest/tests/drivers/pinctrl/api/src/ |
D | main.c | 46 scfg = &pcfg0->states[0]; in ZTEST() 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() 151 scfg = &pcfg0->states[0]; in ZTEST()
|
/Zephyr-latest/tests/subsys/pm/policy_api/ |
D | app.overlay | 11 cpu-power-states = <&state2>; 15 power-states { 43 cpu-power-states = <&state0 &state1>;
|
/Zephyr-latest/include/zephyr/drivers/ |
D | pinctrl.h | 71 const struct pinctrl_state *states; member 187 .states = Z_PINCTRL_STATES_NAME(node_id), \ 193 .states = Z_PINCTRL_STATES_NAME(node_id), \ 440 const struct pinctrl_state *states, 447 const struct pinctrl_state *states, uint8_t state_cnt) in pinctrl_update_states() argument 450 ARG_UNUSED(states); in pinctrl_update_states()
|
/Zephyr-latest/tests/subsys/pm/power_states_api/boards/ |
D | native_sim.overlay | 10 cpu-power-states = <&state0 &state1 &state2 &state3>; 13 power-states { 46 zephyr,disabling-power-states = <&state1 &state2>;
|
/Zephyr-latest/tests/subsys/pm/device_wakeup_api/boards/ |
D | native_sim.overlay | 8 power-states { 24 cpu-power-states = <&state0>;
|
/Zephyr-latest/doc/hardware/peripherals/sensor/ |
D | power_management.rst | 4 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/tests/subsys/pm/power_states_api/src/ |
D | main.c | 19 static enum pm_state states[] = {PM_STATE_SUSPEND_TO_IDLE, enum 56 zassert_true(ARRAY_SIZE(states) == dts_states_len, in ZTEST() 60 zassert_true(memcmp(states, dts_states, ARRAY_SIZE(dts_states)) == 0, in ZTEST()
|
/Zephyr-latest/include/zephyr/pm/ |
D | state.h | 371 uint8_t pm_state_cpu_get_all(uint8_t cpu, const struct pm_state_info **states); 379 static inline uint8_t pm_state_cpu_get_all(uint8_t cpu, const struct pm_state_info **states) in pm_state_cpu_get_all() argument 382 ARG_UNUSED(states); in pm_state_cpu_get_all()
|
/Zephyr-latest/samples/subsys/pm/latency/boards/ |
D | native_sim.overlay | 7 power-states { 30 cpu-power-states = <&runtime_idle &suspend_to_idle &standby>;
|
/Zephyr-latest/tests/subsys/pm/power_mgmt/boards/ |
D | native_sim.overlay | 9 power-states { 44 cpu-power-states = <&state0 &state1>;
|
/Zephyr-latest/subsys/pm/ |
D | state.c | 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/doc/services/pm/ |
D | system.rst | 11 power management subsystem to put an idle system into one of the supported 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: 132 into certain power states. This can be used by devices when executing tasks in
|
D | device.rst | 36 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 { 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 301 lead to undefined behavior or inconsistent states. This API guards such [all …]
|
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
D | sar_cfg_srv.rst | 13 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`.
|
D | brg_cfg_srv.rst | 20 The Bridge Configuration Server model provides access to the following three states: 26 For more information about the states, see :ref:`bluetooth_mesh_brg_cfg_states`.
|
D | sar_cfg_cli.rst | 14 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/samples/boards/st/power_mgmt/suspend_to_ram/boards/ |
D | nucleo_wba55cg.overlay | 11 cpu-power-states = <&stop0 &stop1 &standby>; 14 power-states {
|
/Zephyr-latest/tests/subsys/pm/device_wakeup_api/ |
D | CMakeLists.txt | 7 project(pm-states-test)
|
/Zephyr-latest/tests/subsys/pm/power_states_api/ |
D | CMakeLists.txt | 7 project(pm-states-test)
|
/Zephyr-latest/samples/boards/st/power_mgmt/stop3/boards/ |
D | nucleo_u575zi_q.overlay | 14 cpu-power-states = <&stop0 &stop1 &stop2 &stop3>;
|
/Zephyr-latest/lib/smf/ |
D | smf.c | 36 static const struct smf_state *get_child_of(const struct smf_state *states, in get_child_of() argument 39 const struct smf_state *tmp = states; in get_child_of() 54 static const struct smf_state *get_last_of(const struct smf_state *states) in get_last_of() argument 56 return get_child_of(states, NULL); in get_last_of()
|
/Zephyr-latest/dts/arm/microchip/ |
D | mec172xnsz.dtsi | 29 cpu-power-states = <&idle &suspend_to_ram>; 32 power-states {
|