Home
last modified time | relevance | path

Searched +full:powered +full:- +full:on (Results 1 – 25 of 189) sorted by relevance

12345678

/Zephyr-latest/include/zephyr/drivers/
Dpm_cpu_ops.h4 * SPDX-License-Identifier: Apache-2.0
35 * This call is intended for use in hotplug. A core that is powered down by
36 * cpu_off can only be powered up again in response to a cpu_on
39 * @retval -ENOTSUP If the operation is not supported
47 * into the calling supervisory software or have been previously powered down
50 * @param cpuid CPU id to power on
53 * @retval 0 on success, a negative errno otherwise
54 * @retval -ENOTSUP If the operation is not supported
65 * @retval 0 on success, a negative errno otherwise
/Zephyr-latest/drivers/power_domain/
Dpower_domain_gpio.c5 * SPDX-License-Identifier: Apache-2.0
39 /* Only run action if the device is on the specified domain */ in pd_on_domain_visitor()
40 if (!dev->pm || (dev->pm_base->domain != visitor_context->domain)) { in pd_on_domain_visitor()
44 (void)pm_device_action_run(dev, visitor_context->action); in pd_on_domain_visitor()
56 const struct pd_gpio_config *cfg = dev->config; in pd_gpio_pm_action()
57 struct pd_gpio_data *data = dev->data; in pd_gpio_pm_action()
64 return -ENOTSUP; in pd_gpio_pm_action()
70 k_sleep(data->next_boot); in pd_gpio_pm_action()
71 /* Switch power on */ in pd_gpio_pm_action()
72 gpio_pin_set_dt(&cfg->enable, 1); in pd_gpio_pm_action()
[all …]
/Zephyr-latest/doc/services/pm/
Dpower_domain.rst1 .. _pm-power-domain:
10 powered by a common source to be notified of power source state changes in a
12 that device B is on the same power domain and should also be configured into a
15 Power domains are optional on Zephyr, to enable this feature the
18 When a power domain turns itself on or off, it is the responsibility of the
25 .. _pm-domain-work-flow:
42 action -> devA [label="pm_device_get()"]
43 devA:se -> domain:n [label="pm_device_get()"]
45 domain -> devB [label="action_cb(PM_DEVICE_ACTION_TURN_ON)"]
46 domain:sw -> devA:sw [label="action_cb(PM_DEVICE_ACTION_TURN_ON)"]
[all …]
/Zephyr-latest/dts/bindings/regulator/
Drenesas,da1469x-regulator.yaml2 # SPDX-License-Identifier: Apache-2.0
7 compatible: "renesas,smartbond-regulator"
9 child-binding:
11 - name: regulator.yaml
12 property-allowlist:
13 - regulator-always-on
14 - regulator-boot-on
15 - regulator-init-microvolt
16 - regulator-initial-mode
17 - regulator-max-microamp
[all …]
Dsilabs,series2-dcdc.yaml2 # SPDX-License-Identifier: Apache-2.0
5 Silicon Labs Series 2 DC-DC converter.
7 Include the bindings header file <zephyr/dt-bindings/regulator/silabs_dcdc.h> to get
12 `regulator-boot-on`
13 Enable DC-DC converter at boot. If not set, the DC-DC converter is powered off.
14 `regulator-allow-bypass`
15 Enable bypass mode. If combined with `regulator-boot-on`, the DC-DC converter
17 `regulator-initial-mode`
19 `regulator-init-microvolt`
22 compatible: "silabs,series2-dcdc"
[all …]
/Zephyr-latest/soc/ambiq/apollo3x/
Dpower.c4 * SPDX-License-Identifier: Apache-2.0
15 /* ambiq-sdk includes */
34 /* Cotex-m: power down, register value preserve.*/ in pm_state_set()
54 * to active state on wake up
71 * Currently all flash area is powered on, but we should only enable the used flash area and in ambiq_power_init()
79 * Currently all SRAM area is powered on, but we should only enable the used ram area and in ambiq_power_init()
86 /* For optimal Deep Sleep current, configure cache to be powered-down in deepsleep. */ in ambiq_power_init()
/Zephyr-latest/subsys/usb/device/
DKconfig4 # SPDX-License-Identifier: Apache-2.0
16 module-str = usb device
39 default "USB-DEV"
126 bool "Set Self-powered characteristic"
129 Set Self-powered characteristic in bmAttributes to indicate
130 self powered USB device.
146 This prevents deadlock situations where tasks on the system
148 as UART transmission on CDC-ACM, preventing the system work
149 queue from making progress on the USB tasks that would
157 depends on USB_WORKQUEUE
[all …]
/Zephyr-latest/samples/subsys/usb/common/
DKconfig.sample_usbd2 # SPDX-License-Identifier: Apache-2.0
10 depends on USB_DEVICE_STACK_NEXT
31 bool "USB device sample Self-powered attribute"
34 Set the Self-powered attribute in the sample configuration.
/Zephyr-latest/include/zephyr/arch/common/
Dpm_s2ram.h31 * This function never returns if the system is powered off. If the operation
35 * @retval none The system is powered off.
36 * @retval -EBUSY The system is busy and cannot be powered off at this time.
37 * @retval -errno Other error codes.
42 * @brief Save CPU context on suspend
44 * This function is used on suspend-to-RAM (S2RAM) to save the CPU context in
49 * must be restored on resume to let the platform resume its execution from the
55 * @retval -EBUSY The system is busy and cannot be suspended at this time.
56 * @retval -errno Negative errno code in case of failure.
61 * @brief Mark that core is entering suspend-to-RAM state.
[all …]
/Zephyr-latest/drivers/bbram/
DKconfig.stm322 # SPDX-License-Identifier: Apache-2.0
5 bool "ST STM32 Battery-backed RAM drivers"
7 depends on DT_HAS_ST_STM32_BBRAM_ENABLED
8 depends on COUNTER_RTC_STM32 || RTC_STM32
13 STM32 BBRAM are 32-bit registers which can be used for storing user
15 powered-on by VBAT when the VDD power is switched off. They are not reset
/Zephyr-latest/dts/bindings/power-domain/
Dpower-domain-gpio-monitor.yaml2 # SPDX-License-Identifier: Apache-2.0
8 rail is on/off. Therefore, performing resume/suspend on power domain won't
9 change physical state of power rails and that action won't be triggered on
13 compatible: "power-domain-gpio-monitor"
15 include: power-domain.yaml
19 type: phandle-array
22 GPIO to use to sense if rail is powered on.
24 "#power-domain-cells":
/Zephyr-latest/drivers/retained_mem/
DKconfig2 # SPDX-License-Identifier: Apache-2.0
8 device is powered (may be lost in low power states).
21 depends on MULTITHREADING
22 depends on !RETAINED_MEM_MUTEX_FORCE_DISABLE
26 depends on MULTITHREADING
33 module-str = retained_mem
/Zephyr-latest/drivers/sensor/st/vl53l0x/
DKconfig4 # SPDX-License-Identifier: Apache-2.0
9 depends on DT_HAS_ST_VL53L0X_ENABLED
10 depends on ZEPHYR_HAL_ST_MODULE
14 Enable driver for VL53L0X I2C-based time of flight sensor.
19 depends on VL53L0X
25 depends on VL53L0X
29 must have an xshut-gpio property.
32 value from a sensor, it is powered up and its I2C address is reconfigured
/Zephyr-latest/soc/microchip/mec/mec172x/reg/
Dmec172x_vbat.h4 * SPDX-License-Identifier: Apache-2.0
16 /* Offset 0x00 Power-Fail and Reset Status */
48 /* single ended crystal on XTAL2 instead of parallel across XTAL1 and XTAL2 */
64 /* 32K silicon OSC when chip powered by VBAT or VTR */
66 /* 32K external crystal when chip powered by VBAT or VTR */
68 /* 32K input pin on VTR. Switch to Silicon OSC on VBAT */
70 /* 32K input pin on VTR. Switch to crystal on VBAT */
77 * Monotonic Counter least significant word (32-bit), read-only.
78 * Increments by one on read.
82 /* Monotonic Counter most significant word (32-bit). Read-Write */
/Zephyr-latest/soc/nordic/nrf53/
Dnrf53_cpunet_mgmt.h4 * SPDX-License-Identifier: Apache-2.0
23 * In conseqeuence, if @p on equals @c true then the network CPU is guaranteed to be enabled when
24 * this function returns. If @p on equals @c false then nothing can be inferred about the state of
27 * @param on indicates whether the network CPU shall be powered on or off.
29 void nrf53_cpunet_enable(bool on);
/Zephyr-latest/dts/bindings/timer/
Dnxp,os-timer.yaml2 # SPDX-License-Identifier: Apache-2.0
4 description: NXP OS Timer on i.MX-RT5xx/6xx
6 compatible: "nxp,os-timer"
17 deep-sleep-counter:
20 Instance of a counter peripheral. The OS Timer maybe powered off in
/Zephyr-latest/dts/bindings/memory-controllers/
Dst,stm32-bbram.yaml2 # SPDX-License-Identifier: Apache-2.0
7 STM32 BBRAM are 32-bit registers which can be used for storing user
9 powered-on by VBAT when the VDD power is switched off. They are not reset
13 compatible: "st,stm32-bbram"
18 st,backup-regs:
/Zephyr-latest/drivers/mm/
DKconfig3 # SPDX-License-Identifier: Apache-2.0
23 Allows TLB driver to remap unused RAM - unused
26 Note that unused memory will be powered off by
33 depends on DT_HAS_INTEL_ADSP_MTL_TLB_ENABLED
36 Driver for the translation lookup buffer on
42 depends on DT_HAS_INTEL_ADSP_TLB_ENABLED
44 Driver for the translation lookup buffer on
49 depends on !MMU
59 depends on EXTERNAL_ADDRESS_TRANSLATION
/Zephyr-latest/tests/subsys/pm/device_power_domains/src/
Dmain.c5 * SPDX-License-Identifier: Apache-2.0
46 TC_PRINT("Enabling runtime power management on regulators\n"); in ZTEST()
61 TC_PRINT("Cycling: %s\n", reg_0->name); in ZTEST()
63 /* reg_chained is powered off reg_0, so it's power state should change */ in ZTEST()
70 TC_PRINT("Cycling: %s\n", reg_1->name); in ZTEST()
75 /* dev is on reg_1, should have automatically moved to suspended */ in ZTEST()
82 TC_PRINT("Cycling: %s\n", reg_chained->name); in ZTEST()
84 /* reg_chained should be powered after being requested */ in ZTEST()
88 /* dev is not on reg_chained but does reference it, should still be in OFF */ in ZTEST()
93 TC_PRINT("Requesting dev: %s\n", dev->name); in ZTEST()
[all …]
/Zephyr-latest/soc/espressif/esp32c2/
DKconfig2 # SPDX-License-Identifier: Apache-2.0
19 bool "Power down MAC and baseband of Wi-Fi and Bluetooth when PHY is disabled"
20 depends on SOC_SERIES_ESP32C2 && TICKLESS_KERNEL
22 If enabled, the MAC and baseband of Wi-Fi and Bluetooth will be powered
24 by a small amount but increases RAM use by approximately 4 KB(Wi-Fi only),
25 2 KB(Bluetooth only) or 5.3 KB(Wi-Fi + Bluetooth).
/Zephyr-latest/samples/boards/nordic/system_off/
DREADME.rst1 .. zephyr:code-sample:: nrf_system_off
3 :relevant-api: sys_poweroff subsys_pm_device
5 Use deep sleep on Nordic platforms.
11 deep sleep on Nordic platforms.
18 number of times system off was entered, and total uptime since initial power-on
20 RAM is configured to keep the containing section powered while in system-off mode.
31 -----------------
33 .. code-block:: console
35 *** Booting Zephyr OS build v2.3.0-rc1-204-g5f2eb85f728d ***
/Zephyr-latest/soc/espressif/esp32c6/
DKconfig2 # SPDX-License-Identifier: Apache-2.0
22 bool "Power down MAC and baseband of Wi-Fi and Bluetooth when PHY is disabled"
23 depends on SOC_SERIES_ESP32C6 && TICKLESS_KERNEL
25 If enabled, the MAC and baseband of Wi-Fi and Bluetooth will be powered
27 by a small amount but increases RAM use by approximately 4 KB(Wi-Fi only),
28 2 KB(Bluetooth only) or 5.3 KB(Wi-Fi + Bluetooth).
/Zephyr-latest/lib/mem_blocks/
DKconfig3 # SPDX-License-Identifier: Apache-2.0
14 This is useful for operations such as scatter-gather DMA
19 powered down to conserve energy.
23 depends on SYS_MEM_BLOCKS
27 events, such as memory allocation and de-allocation.
31 depends on SYS_MEM_BLOCKS
39 depends on SYS_MEM_BLOCKS && OBJ_CORE
47 depends on SYS_MEM_BLOCKS && OBJ_CORE_STATS
/Zephyr-latest/samples/boards/st/power_mgmt/wkup_pins/
DREADME.rst1 .. zephyr:code-sample:: stm32_pm_gpio_wkup_src
2 :name: GPIO as a wake-up pin source
3 :relevant-api: sys_poweroff gpio_interface
5 Use a GPIO as a wake-up pin source.
10 This sample is a minimum application to demonstrate using a wake-up pin with a GPIO as
11 a source to power on an STM32 SoC after Poweroff.
14 Press the user button designated in boards's devicetree overlay as "wkup-src" to power it on again.
16 .. _gpio-as-a-wkup-pin-src-sample-requirements:
21 The SoC should support POWEROFF functionality & have a wake-up pin that corresponds
24 Make sure that wake-up pins are configured in SoC dtsi file.
[all …]
/Zephyr-latest/boards/norik/octopus_io_board/doc/
Dindex.rst6 Octopus IO-Board is an expansion to the Octopus SoM, which is built around the nRF9160 SiP
7 offering NB-IoT and LTE-M connectivity, GPS and accelerometer. Octopus IO-Board expands
9 development and prototyping of low-power IoT applications.
11 nRF9160 SiP contains ARM Cortex-M33 application processor and the
18 * :abbr:`I2C (Inter-Integrated Circuit)`
25 * :abbr:`UARTE (Universal asynchronous receiver-transmitter with EasyDMA)`
29 Octopus IO-Board offers the following features:
32 * USB-C for power
41 * Tag-Connect TC2030-IDC 6-pin connector for SWD programming and debugging
44 More information about the board can be found at the `Octopus IO-Board Product Page`_
[all …]

12345678