Home
last modified time | relevance | path

Searched +full:power +full:- +full:managed (Results 1 – 25 of 619) sorted by relevance

12345678910>>...25

/openbmc/linux/arch/arm64/boot/dts/freescale/
H A Dfsl-lx2160a-clearfog-itx.dtsi1 // SPDX-License-Identifier: (GPL-2.0 OR MIT)
8 /dts-v1/;
10 #include "fsl-lx2160a-cex7.dtsi"
11 #include <dt-bindings/input/linux-event-codes.h>
20 stdout-path = "serial0:115200n8";
23 gpio-keys {
24 compatible = "gpio-keys";
27 label = "power";
28 linux,can-disable;
34 sfp0: sfp-0 {
[all …]
H A Dfsl-ls1088a-ten64.dts1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
4 * Based on fsl-ls1088a-rdb.dts
5 * Copyright 2017-2020 NXP
6 * Copyright 2019-2021 Traverse Technologies
11 /dts-v1/;
13 #include "fsl-ls1088a.dtsi"
15 #include <dt-bindings/gpio/gpio.h>
16 #include <dt-bindings/input/input.h>
28 stdout-path = "serial0:115200n8";
32 compatible = "gpio-keys";
[all …]
H A Dfsl-ls1028a-kontron-kbox-a-230-ls.dts1 // SPDX-License-Identifier: GPL-2.0+
3 * Device Tree File for the Kontron KBox A-230-LS.
5 * This consists of a Kontron SMARC-sAL28 (Dual PHY) and a special
12 /dts-v1/;
13 #include "fsl-ls1028a-kontron-sl28-var4.dts"
14 #include <dt-bindings/leds/common.h>
17 model = "Kontron KBox A-230-LS";
18 compatible = "kontron,kbox-a-230-ls", "kontron,sl28-var4",
22 compatible = "gpio-leds";
24 alarm-led {
[all …]
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Logging/
H A DErrorBlocksTransition.interface.yaml3 prevent a state transition of the associated managed element while the
7 A typical use of this would be to prevent the power-on of a managed host
8 while a critical error is open. The managed host, via systemd transitions,
9 might start the power-on sequence and then wait for any object with this
11 ordering of D-Bus operations can prove that no critical error needs
12 servicing and the power-on sequence may safely continue.
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Software/
H A DActivationBlocksTransition.interface.yaml3 prevent a state transition of the associated managed element while the
7 A typical use of this would be to prevent (delay) the power-on of a managed
8 host while the BIOS is being updated. The managed host, via systemd
9 transitions, might start the power-on sequence and then wait for any object
12 update is currently being performed and the power-on sequence may safely
/openbmc/linux/include/drm/
H A Ddrm_device.h27 * enum switch_power_state - power state of drm device
31 /** @DRM_SWITCH_POWER_ON: Power state is ON */
34 /** @DRM_SWITCH_POWER_OFF: Power state is OFF */
37 /** @DRM_SWITCH_POWER_CHANGING: Power state is changing */
45 * struct drm_device - DRM device structure
54 /** @ref: Object ref-count */
57 /** @dev: Device structure of bus-device */
61 * @managed:
63 * Managed resources linked to the lifetime of this &drm_device as
67 /** @managed.resources: managed resources list */
[all …]
/openbmc/intel-ipmi-oem/
H A Dipmi-allowlist.conf8 0x00:0x06:0x7f7f //<Chassis>:<Set Power Restore Policy>
34 0x04:0x2a:0x7f7f //<Sensor/Event>:<Re-arm Sensor Events>
44 0x06:0x06:0xffff //<App>:<Set ACPI Power State>
45 0x06:0x07:0xffff //<App>:<Get ACPI Power State>
174 0x2e:0xCB:0x7f7f //<Intel OEM>:<Set Node Manager Power Draw Range>
177 0x2e:0xD0:0x7f7f //<Intel OEM>:<Set Total Power Budget>
178 0x2e:0xD1:0xff7f //<Intel OEM>:<Get Total Power Budget>
179 0x2e:0xD2:0x7f7f //<Intel OEM>:<Set Max Allowed CPU P-state/Threads>
180 0x2e:0xD3:0xff7f //<Intel OEM>:<Get Max Allowed CPU P-state/Threads>
181 0x2e:0xD4:0xff7f //<Intel OEM>:<Get Number of P-states/Threads>
[all …]
/openbmc/linux/Documentation/devicetree/bindings/bus/
H A Dsimple-pm-bus.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/bus/simple-pm-bus.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Simple Power-Managed Bus
10 - Geert Uytterhoeven <geert+renesas@glider.be>
13 A Simple Power-Managed Bus is a transparent bus that doesn't need a real
19 on-SoC or externally) to function.
21 While "simple-pm-bus" follows the "simple-bus" set of properties, as
23 "simple-bus".
[all …]
/openbmc/openbmc/meta-yadro/meta-vegman/recipes-phosphor/leds/rx20-led-manager-config/
H A Dled.yaml5 # Managed by callback-manager
60 # Power button indication
61 # Managed by phosphor-dbus-monitor
98 # Managed by phosphor-dbus-monitor
133 # Managed by phosphor-dbus-monitor
/openbmc/u-boot/include/
H A Dpower-domain.h1 /* SPDX-License-Identifier: GPL-2.0 */
10 * A power domain is a portion of an SoC or chip that is powered by a
11 * switchable source of power. In many cases, software has control over the
12 * power domain, and can turn the power source on or off. This is typically
13 * done to save power by powering off unused devices, or to enable software
15 * drivers to turn power domains on and off.
17 * A driver that implements UCLASS_POWER_DOMAIN is a power domain controller or
18 * provider. A controller will often implement multiple separate power domains,
20 * power-domain-uclass.h describes the interface which power domain controllers
23 * Depending on the power domain controller hardware, changing the state of a
[all …]
/openbmc/linux/Documentation/devicetree/bindings/sound/
H A Dcs35l32.txt5 - compatible : "cirrus,cs35l32"
7 - reg : the I2C address of the device for I2C. Address is determined by the level
10 - VA-supply, VP-supply : power supplies for the device,
15 - reset-gpios : a GPIO spec for the reset pin. If specified, it will be
18 - cirrus,boost-manager : Boost voltage control.
19 0 = Automatically managed. Boost-converter output voltage is the higher
21 1 = Automatically managed irrespective of audio, adapting for low-power
22 dissipation when LEDs are ON, and operating in Fixed-Boost Bypass Mode
27 - cirrus,sdout-datacfg : Data configuration for dual CS35L32 applications only.
28 Determines the data packed in a two-CS35L32 configuration.
[all …]
/openbmc/linux/arch/arm/boot/dts/microchip/
H A Dlan966x-kontron-kswitch-d10-mmt-6g-2gs.dts1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
3 * Device Tree file for the Kontron KSwitch D10 MMT 6G-2GS
6 /dts-v1/;
7 #include "lan966x-kontron-kswitch-d10-mmt.dtsi"
10 model = "Kontron KSwitch D10 MMT 6G-2GS";
11 compatible = "kontron,kswitch-d10-mmt-6g-2gs", "kontron,s1921",
21 i2c-bus = <&i2c4>;
22 los-gpios = <&sgpio_in 1 0 GPIO_ACTIVE_HIGH>;
23 mod-def0-gpios = <&sgpio_in 1 1 GPIO_ACTIVE_LOW>;
24 maximum-power-milliwatt = <2500>;
[all …]
/openbmc/linux/include/linux/
H A Dscmi_protocol.h1 /* SPDX-License-Identifier: GPL-2.0-only */
5 * Copyright (C) 2018-2021 ARM Ltd.
21 * struct scmi_revision_info - version information structure
30 * @impl_ver: A vendor-specific implementation version.
32 * @sub_vendor_id: A sub-vendor identifier(Null terminated ASCII string)
74 * struct scmi_clk_proto_ops - represents the various operations provided
106 * struct scmi_perf_proto_ops - represents the various operations provided
122 * @est_power_get: gets the estimated power cost for a given performance domain
126 * @power_scale_mw_get: indicates if the power values provided are in milliWatts
151 unsigned long *rate, unsigned long *power);
[all …]
H A Dreset.h1 /* SPDX-License-Identifier: GPL-2.0 */
14 * struct reset_control_bulk_data - Data used for bulk reset control operations.
114 return optional ? 0 : -ENOTSUPP; in __device_reset()
122 return optional ? NULL : ERR_PTR(-ENOTSUPP); in __of_reset_control_get()
130 return optional ? NULL : ERR_PTR(-ENOTSUPP); in __reset_control_get()
167 return optional ? 0 : -EOPNOTSUPP; in __reset_control_bulk_get()
180 return optional ? NULL : ERR_PTR(-ENOTSUPP); in __devm_reset_control_get()
188 return optional ? 0 : -EOPNOTSUPP; in __devm_reset_control_bulk_get()
194 return optional ? NULL : ERR_PTR(-ENOTSUPP); in devm_reset_control_array_get()
201 return optional ? NULL : ERR_PTR(-ENOTSUPP); in of_reset_control_array_get()
[all …]
/openbmc/linux/arch/arm64/boot/dts/marvell/
H A Darmada-3720-uDPU.dtsi1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
4 * Based on Marvell Armada 3720 development board (DB-88F3720-DDR3)
12 /dts-v1/;
14 #include <dt-bindings/gpio/gpio.h>
15 #include "armada-372x.dtsi"
19 stdout-path = "serial0:115200n8";
28 compatible = "gpio-leds";
30 led-power1 {
31 label = "udpu:green:power";
35 led-power2 {
[all …]
/openbmc/openbmc/meta-yadro/meta-vegman/recipes-phosphor/leds/vegman-led-manager-config/
H A Dled.yaml5 # Managed by callback-manager
8 # See https://j.yadro.com/browse/BBMC-221 for details.
66 # Power button indication
67 # Managed by phosphor-dbus-monitor
/openbmc/linux/tools/testing/selftests/cpufreq/
H A Dcpufreq.sh2 # SPDX-License-Identifier: GPL-2.0
17 if [ ! -d $CPUROOT/$1/cpufreq ]; then
24 if [ -d $CPUROOT/$1/cpufreq ]; then
31 policies=$(ls $CPUFREQROOT| grep "policy[0-9].*")
39 policies=$(ls $CPUFREQROOT| grep "policy[0-9].*")
53 if [ -f $1/$file ]; then
71 printf "%s\n\n" "------------------------------------------------"
85 if [ -f $1/$file ]; then
87 local wfile=$(ls -l $1/$file | awk '$1 ~ /^.*w.*/ { print $NF; }')
89 if [ ! -z $wfile ]; then
[all …]
/openbmc/linux/drivers/video/backlight/
H A Dlcd.c1 // SPDX-License-Identifier: GPL-2.0-only
5 * Copyright (C) 2003,2004 Hewlett-Packard Company
25 * and if it is, we're switching lcd power as well ...
34 if (!ld->ops) in fb_notifier_callback()
37 mutex_lock(&ld->ops_lock); in fb_notifier_callback()
38 if (!ld->ops->check_fb || ld->ops->check_fb(ld, evdata->info)) { in fb_notifier_callback()
40 if (ld->ops->set_power) in fb_notifier_callback()
41 ld->ops->set_power(ld, *(int *)evdata->data); in fb_notifier_callback()
43 if (ld->ops->set_mode) in fb_notifier_callback()
44 ld->ops->set_mode(ld, evdata->data); in fb_notifier_callback()
[all …]
/openbmc/linux/Documentation/devicetree/bindings/soc/ti/
H A Dsci-pm-domain.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/soc/ti/sci-pm-domain.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: TI-SCI generic power domain
10 - Nishanth Menon <nm@ti.com>
13 - $ref: /schemas/power/power-domain.yaml#
16 Some TI SoCs contain a system controller (like the Power Management Micro
20 through a protocol called TI System Control Interface (TI-SCI protocol).
22 This PM domain node represents the global PM domain managed by the TI-SCI
[all …]
/openbmc/linux/Documentation/driver-api/driver-model/
H A Ddevres.rst2 Devres - Managed Device Resource
16 6. List of managed interfaces: Currently implemented managed interfaces
20 --------
29 sufficient bugs in ->remove and ->probe failure path. Well, yes,
42 and having half broken failure path implementation in ->probe() which
48 ---------
57 Managed interface is created for resources commonly used by device
59 using dma_alloc_coherent(). The managed version is called
61 for the DMA memory allocated using it is managed and will be
75 dma_free_coherent(dev, this->size, this->vaddr, this->dma_handle);
[all …]
/openbmc/linux/Documentation/devicetree/bindings/phy/
H A Damlogic,g12a-usb2-phy.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/phy/amlogic,g12a-usb2-phy.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Neil Armstrong <neil.armstrong@linaro.org>
16 - amlogic,g12a-usb2-phy
17 - amlogic,a1-usb2-phy
25 clock-names:
27 - const: xtal
32 reset-names:
[all …]
/openbmc/u-boot/doc/device-tree-bindings/power/
H A Dti,sci-pm-domain.txt1 Texas Instruments TI SCI Generic Power Domain
13 The PM domain node represents the global PM domain managed by the SYSFW. Because
18 --------------------
19 - compatible: Must be "ti,sci-pm-domain"
20 - #power-domain-cells: Must be 1 so that an id can be provided in each
24 ----------------
26 compatible = "ti,am654-system-controller";
28 k3_pds: power-controller {
29 compatible = "ti,sci-pm-domain";
30 #power-domain-cells = <1>;
[all …]
/openbmc/linux/Documentation/driver-api/
H A Ddevice_link.rst27 In its standard or *managed* form, a device link combines *both* dependency
57 device ``->probe`` callback or a boot-time PCI quirk.
61 ``->probe`` callback while the supplier hasn't started to probe yet: Had the
65 non-presence. [Note that it is valid to create a link from the consumer's
66 ``->probe`` callback while the supplier is still probing, but the consumer must
72 is added in the ``->probe`` callback of the supplier or consumer driver, it is
73 typically deleted in its ``->remove`` callback for symmetry. That way, if the
77 to deletion. Device links managed by the driver core are deleted automatically
87 link is added from the consumer's ``->probe`` callback: ``DL_FLAG_RPM_ACTIVE``
93 Similarly, when the device link is added from supplier's ``->probe`` callback,
[all …]
/openbmc/linux/sound/soc/sof/intel/
H A Dicl.c1 // SPDX-License-Identifier: (GPL-2.0-only OR BSD-3-Clause)
16 #include "../ipc4-priv.h"
19 #include "hda-ipc.h"
20 #include "../sof-audio.h"
32 struct sof_intel_hda_dev *hda = sdev->pdata->hw_pdata; in icl_dsp_core_stall()
33 const struct sof_intel_dsp_desc *chip = hda->desc; in icl_dsp_core_stall()
35 /* make sure core_mask in host managed cores */ in icl_dsp_core_stall()
36 core_mask &= chip->host_managed_cores_mask; in icl_dsp_core_stall()
38 dev_err(sdev->dev, "error: core_mask is not in host managed cores\n"); in icl_dsp_core_stall()
39 return -EINVAL; in icl_dsp_core_stall()
[all …]
/openbmc/linux/Documentation/devicetree/bindings/usb/
H A Dwillsemi,wusb3801.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: WUSB3801 Type-C port controller
10 The Will Semiconductor WUSB3801 is a USB Type-C port controller which
12 compatible with the USB Type-C Cable and Connector Specification v1.2.
15 - Samuel Holland <samuel@sholland.org>
20 - willsemi,wusb3801
30 $ref: ../connector/usb-connector.yaml#
33 The managed USB Type-C connector. Since WUSB3801 does not support
[all …]

12345678910>>...25