Searched +full:power +full:- +full:on (Results 1 – 25 of 1040) sorted by relevance
12345678910>>...42
| /Zephyr-latest/subsys/pm/ |
| D | Kconfig | 1 # Copyright (c) 2014-2015 Wind River Systems, Inc.
3 # SPDX-License-Identifier: Apache-2.0
5 menu "Power Management"
11 calls to configure low-power states.
14 bool "System Power Management"
15 depends on SYS_CLOCK_EXISTS && HAS_PM
17 This option enables the board to implement extra power management
19 power management subsystem of the number of ticks until the next kernel
27 module-str = System Power Management
31 bool "System Power Management Stats"
[all …]
|
| /Zephyr-latest/drivers/power_domain/ |
| D | Kconfig | 2 # SPDX-License-Identifier: Apache-2.0
5 bool "Power domain drivers"
7 Include drivers for power domains in system config
12 module-str = power_domain
16 int "Power domain init priority"
19 Power domain initialization priority.
22 bool "GPIO controlled power domain"
24 depends on DT_HAS_POWER_DOMAIN_GPIO_ENABLED
25 depends on GPIO
26 depends on PM_DEVICE || !PM_DEVICE_POWER_DOMAIN
[all …]
|
| /Zephyr-latest/dts/bindings/power-domain/ |
| D | power-domain-gpio-monitor.yaml | 2 # SPDX-License-Identifier: Apache-2.0
5 Simple monitorig power domain
7 This power domain monitors the state of a GPIO pin to detect whether a power
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
11 pending transaction won't be interrupted by power state change.
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.
[all …]
|
| /Zephyr-latest/doc/services/pm/ |
| D | power_domain.rst | 1 .. _pm-power-domain:
3 Power Domain
9 The Zephyr power domain abstraction is designed to support groupings of devices
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
13 low power state.
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
19 power domain to notify all devices using it through their power management
25 .. _pm-domain-work-flow:
[all …]
|
| D | device.rst | 1 Device Power Management
7 Device power management (PM) on Zephyr is a feature that enables devices to
10 selected, device drivers implementing power management will be able to take
11 advantage of the device power management subsystem.
13 Zephyr supports two methods of device power management:
15 - :ref:`Device Runtime Power Management <pm-device-runtime-pm>`
16 - :ref:`System-Managed Device Power Management <pm-device-system-pm>`
18 .. _pm-device-runtime-pm:
20 Device Runtime Power Management
23 Device runtime power management involves coordinated interaction between
[all …]
|
| D | system.rst | 1 .. _pm-system:
3 System Power Management
11 power management subsystem to put an idle system into one of the supported power states.
13 the appropriate power state to transition to based on the configured power management policy.
15 It is the application's responsibility to set up a wake-up event.
16 A wake-up event will typically be an interrupt triggered by an SoC peripheral module.
18 Keep in mind that depending on the SoC and the power mode in question,
20 some wake-up sources may not be usable in all power modes.
22 The following diagram describes system power management:
25 :caption: System power management
[all …]
|
| D | device_runtime.rst | 1 .. _pm-device-runtime:
3 Device Runtime Power Management
9 The device runtime power management (PM) framework is an active power management
10 mechanism which reduces the overall system power consumption by suspending the
15 on usage count.
17 When device runtime power management is enabled on a device, its state will be
19 not used. On the first device request, it will be resumed and so put into the
29 For devices on a power domain (via the devicetree 'power-domains' property), device runtime
30 power management automatically attempts to request and release the dependent domain
32 calls on the child device.
[all …]
|
| /Zephyr-latest/dts/bindings/sensor/ |
| D | ti,ina230.yaml | 5 # SPDX-License-Identifier: Apache-2.0
9 TI INA230, INA231 and INA236 Bidirectional Current and Power Monitor.
10 The <zephyr/dt-bindings/sensor/ina230.h> file should be included in the
16 include: ti,ina23x-common.yaml
28 alert-config:
30 description: Diag alert register, default matches the power-on reset value
32 adc-mode:
36 Default is the power-on reset value.
39 - "Shutdown single shot"
40 - "Shunt Voltage single shot"
[all …]
|
| D | ti,fdc2x1x.yaml | 2 # SPDX-License-Identifier: Apache-2.0
8 include: [sensor-device.yaml, i2c-device.yaml]
11 sd-gpios:
12 type: phandle-array
18 intb-gpios:
19 type: phandle-array
28 Set to identify the sensor as FDC2114 or FDC2214 (4-channel version)
33 Set the Auto-Scan Mode.
35 false = Continuous conversion on the single channel selected by
36 "active-channel" (single channel mode).
[all …]
|
| D | ti,ina237.yaml | 4 # SPDX-License-Identifier: Apache-2.0
8 TI INA237 Bidirectional Current and Power Monitor.
9 The <zephyr/dt-bindings/sensor/ina237.h> file should be included in the
15 include: ti,ina23x-common.yaml
31 adc-config:
41 alert-config:
43 description: Diag alert register, default matches the power-on reset value
45 adc-mode:
49 Default is the power-on reset value.
52 - "Shutdown single shot"
[all …]
|
| D | ti,ina226.yaml | 2 # SPDX-License-Identifier: Apache-2.0
5 TI INA226 Bidirectional Current and Power Monitor.
6 The <zephyr/dt-bindings/sensor/ina226.h> file should be included in the
12 include: [sensor-device.yaml, i2c-device.yaml]
15 avg-count:
19 Default is the power-on reset value.
23 vbus-conversion-time-us:
27 Default is the power-on reset value.
31 vshunt-conversion-time-us:
35 Default is the power-on reset value.
[all …]
|
| D | invensense,icm42670.yaml | 4 # SPDX-License-Identifier: Apache-2.0
6 description: ICM-42670 motion tracking device
8 include: [sensor-device.yaml]
11 int-gpios:
12 type: phandle-array
14 The INT signal default configuration is active-high. The
18 accel-hz:
22 Default frequency of accelerometer. (Unit - Hz)
24 Power-on reset value is 800.
26 - 0
[all …]
|
| /Zephyr-latest/subsys/pm/policy/ |
| D | Kconfig | 2 # SPDX-License-Identifier: Apache-2.0
6 prompt "Idle State Power Management Policy"
9 Select the idle state power management policy.
15 on CPU residency times and other constraints imposed by the drivers or
27 bool "Power state constraints per device"
29 This option allows devices to have a list of power states
30 that when the system transition to them, cause power loss in the device.
31 This used to set and release power state constraints when
38 depends on !PM
41 requirements on systems that do not support PM (e.g. systems whithout
[all …]
|
| /Zephyr-latest/drivers/pm_cpu_ops/ |
| D | Kconfig | 1 # CPU power management driver configuration options
4 # SPDX-License-Identifier: Apache-2.0
7 bool "CPU power management drivers"
9 Enable CPU power management drivers configuration
14 module-str = pm_cpu_ops
21 bool "Support for the ARM Power State Coordination Interface (PSCI)"
23 depends on DT_HAS_ARM_PSCI_0_2_ENABLED || DT_HAS_ARM_PSCI_1_1_ENABLED
28 implementing the PSCI specification for CPU-centric power
30 0022A ("Power State Coordination Interface System Software on
35 depends on SHELL && PM_CPU_OPS_PSCI
|
| /Zephyr-latest/drivers/counter/ |
| D | Kconfig.mcux_snvs | 4 # SPDX-License-Identifier: Apache-2.0
9 depends on DT_HAS_NXP_IMX_SNVS_RTC_ENABLED
11 Enable support for the IMX SNVS High/Low Power clock.
14 bool "IMX SNVS SRTC low power support"
15 depends on COUNTER_MCUX_SNVS
18 Enable the low power SRTC in SNVS to synchronise.
21 bool "IMX SNVS wake-up on SRTC alarm"
22 depends on COUNTER_MCUX_SNVS_SRTC
25 Assert Wake-Up Interrupt on SRTC alarm
|
| /Zephyr-latest/soc/nuvoton/npcx/common/ |
| D | power.c | 4 * SPDX-License-Identifier: Apache-2.0
9 * @brief Nuvoton NPCX power management driver
11 * This file contains the drivers of NPCX Power Manager Modules that improves
12 * the efficiency of ec operation by adjusting the chip’s power consumption to
14 * summarizes the main properties of the various power states and shows the
15 * activity levels of the various clocks while in these power states.
17 * +--------------------------------------------------------------------------+
18 * | Power State | LFCLK | HFCLK | APB/AHB | Core | RAM/Regs | VCC | VSBY |
19 * |--------------------------------------------------------------------------|
20 * | Active | On | On | On | Active | Active | On | On |
[all …]
|
| /Zephyr-latest/samples/sensor/sgp40_sht4x/ |
| D | Kconfig | 4 # SPDX-License-Identifier: Apache-2.0
14 bool "Use the Heater on the SHT4X"
23 depends on APP_USE_HEATER
26 int "Heater Power Setting"
29 depends on APP_USE_HEATER
31 0 -> High power heater pulse -> ~200 mW @3.3V
32 1 -> Medium power heater pulse -> ~110 mW @3.3V
33 2 -> Low power heater pulse -> ~20 mW @3.3V
39 depends on APP_USE_HEATER
41 0 -> Long heater pulse -> 1.1s
[all …]
|
| /Zephyr-latest/drivers/wifi/nrf_wifi/ |
| D | Kconfig.nrfwifi | 1 # Nordic Wi-Fi driver for nRF70 series SoCs
5 # SPDX-License-Identifier: Apache-2.0
16 depends on \
21 Nordic Wi-Fi Driver
38 bool "low power mode in QSPI"
52 depends on WIFI_NRF7002 || WIFI_NRF7001
70 depends on WIFI_NRF7002 || WIFI_NRF7001
98 depends on WIFI_NM_WPA_SUPPLICANT_AP
124 bool "Wi-Fi interface auto start on boot"
129 depends on !BUILD_ONLY_NO_BLOBS
[all …]
|
| /Zephyr-latest/dts/bindings/mtd/ |
| D | jedec,spi-nor-common.yaml | 3 # SPDX-License-Identifier: Apache-2.0
5 # Common properties used by nodes describing M25P80-compatible SPI NOR
8 # This extends JESD216-defined features with additional functionality
9 # that may be specific to the vendor of a M25P80-compatible device and
17 requires-ulbpr:
23 protection register that initializes to write-protected. Use this
27 has-dpd:
33 Power-Down mode that is entered by command 0xB9 to reduce power
35 implies that the RDPD (0xAB) Release from Deep Power Down command
36 is also supported. (On some chips this command functions as Read
[all …]
|
| /Zephyr-latest/dts/bindings/led/ |
| D | ti,lp5562.yaml | 5 include: i2c-device.yaml
8 red-output-current:
11 description: Output current of red channel in 0.1 mA (0-25.5 mA).
12 Default value is the power-on default. Valid range = 0 - 255
13 green-output-current:
16 description: Output current of green channel in 0.1 mA (0-25.5 mA)
17 Default value is the power-on default. Valid range = 0 - 255
18 blue-output-current:
21 description: Output current of blue channel in 0.1 mA (0-25.5 mA)
22 Default value is the power-on default. Valid range = 0 - 255
[all …]
|
| /Zephyr-latest/samples/bluetooth/hci_pwr_ctrl/ |
| D | README.rst | 1 .. zephyr:code-sample:: bluetooth_hci_pwr_ctrl
2 :name: HCI Power Control
3 :relevant-api: bt_hrs bluetooth
5 Dynamically control the Tx power of a Bluetooth LE Controller using HCI vendor-specific commands.
10 This sample application demonstrates the dynamic Tx power control over the LL
12 peripheral advertising with varying Tx power. The initial advertiser TX power
13 for the first 5s of the application is the Kconfig set default TX power. Then,
14 the TX power variation of the advertiser is a repeatedly descending staircase
15 pattern ranging from -4 dBm to -30 dBm where the Tx power levels decrease every
19 the Tx power of the peripheral device is modulated per connection accordingly
[all …]
|
| /Zephyr-latest/drivers/sensor/st/lis2dh/ |
| D | Kconfig | 4 # SPDX-License-Identifier: Apache-2.0
9 depends on DT_HAS_ST_LIS2DH_ENABLED
13 Enable SPI/I2C-based driver for LIS2DH, LIS3DH, LSM303DLHC,
28 depends on GPIO
29 depends on $(dt_compat_any_has_prop,$(DT_COMPAT_ST_LIS2DH),irq-gpios)
34 depends on GPIO
35 depends on $(dt_compat_any_has_prop,$(DT_COMPAT_ST_LIS2DH),irq-gpios)
45 depends on LIS2DH_TRIGGER_OWN_THREAD
52 depends on LIS2DH_TRIGGER_OWN_THREAD
67 bool "+/-2g"
[all …]
|
| /Zephyr-latest/dts/bindings/pinctrl/ |
| D | pincfg-node.yaml | 2 # SPDX-License-Identifier: Apache-2.0
15 This is based on Linux, documentation:
16 https://www.kernel.org/doc/Documentation/devicetree/bindings/pinctrl/pincfg-node.yaml
19 bias-disable:
23 bias-high-impedance:
25 description: high impedance mode ("third-state", "floating")
27 bias-bus-hold:
31 bias-pull-up:
33 description: enable pull-up resistor
35 bias-pull-down:
[all …]
|
| /Zephyr-latest/samples/boards/st/power_mgmt/wkup_pins/ |
| D | README.rst | 1 .. 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.
13 The system will power off automatically ``WAIT_TIME_US`` us after boot.
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
[all …]
|
| /Zephyr-latest/include/zephyr/drivers/ |
| D | pm_cpu_ops.h | 4 * SPDX-License-Identifier: Apache-2.0
12 * @brief Public API for CPU Power Management
27 * @defgroup power_management_cpu_api CPU Power Management
33 * @brief Power down the calling core
39 * @retval -ENOTSUP If the operation is not supported
44 * @brief Power up a core
46 * This call is used to power up cores that either have not yet been booted
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
[all …]
|
12345678910>>...42
