| /openbmc/u-boot/doc/device-tree-bindings/video/ |
| H A D | intel-gma.txt | 9 - compatible : "intel,gma";
12 - intel,dp-hotplug : values for digital port hotplug, one cell per value for
14 - intel,panel-port-select : output port to use: 0=LVDS 1=DP_B 2=DP_C 3=DP_D
15 - intel,panel-power-cycle-delay : T4 time sequence (6 = 500ms)
18 - intel,panel-power-up-delay : T1+T2 time sequence
19 - intel,panel-power-down-delay : T3 time sequence
20 - intel,panel-power-backlight-on-delay : T5 time sequence
21 - intel,panel-power-backlight-off-delay : Tx time sequence
23 - intel,cpu-backlight : Value for CPU Backlight PWM
24 - intel,pch-backlight : Value for PCH Backlight PWM
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | OutletGroup.v1_2_0.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
34 "description": "The available OEM-specific actions for this resource.",
35 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
43 …"longDescription": "This Redfish Specification-described type shall contain links to resources tha…
45 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
62 …operties contained in this object shall conform to the Redfish Specification-described requirement…
75 "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/count"
87 "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/count"
[all …]
|
| H A D | Outlet.v1_4_4.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
34 "description": "The available OEM-specific actions for this resource.",
35 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
45 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
117 …"longDescription": "This Redfish Specification-described type shall contain links to resources tha…
119 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
157 "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/count"
164 …property is used to show a connection to an input circuit downstream in a power distribution chain…
[all …]
|
| H A D | Circuit.v1_8_1.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
37 "description": "The available OEM-specific actions for this resource.",
38 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
46 …"longDescription": "This action shall control the state of the circuit breaker or over-current pro…
50 … "description": "The desired power state of the circuit if the breaker is reset successfully.",
51 … "longDescription": "This parameter shall contain the desired power state of the circuit."
55 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
71 "format": "uri-reference",
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
| H A D | OutletGroup_v1.xml | 1 <?xml version="1.0" encoding="UTF-8"?>
2 <!---->
3 <!--################################################################################ -->
4 <!--# Redfish Schema: OutletGroup v1.2.0 -->
5 <!--# -->
6 <!--# For a detailed change log, see the README file contained in the DSP8010 bundle, -->
7 <!--# available at http://www.dmtf.org/standards/redfish -->
8 <!--# Copyright 2014-2024 DMTF. -->
9 <!--# For the full DMTF copyright policy, see http://www.dmtf.org/about/policies/copyright -->
10 <!--################################################################################ -->
[all …]
|
| /openbmc/phosphor-fan-presence/presence/ |
| H A D | anyof.hpp | 42 * @param[in] fan - The fan associated with the policy.
43 * @param[in] s - The set of sensors associated with the policy.
44 * @param[in] e - EEPROM device instance
53 * @param[in] fan - The fan associated with the policy.
54 * @param[in] s - The set of sensors associated with the policy.
67 * @param[in] present - The new presence state according
69 * @param[in] sensor - The sensor reporting the new state.
83 * agree on the presence value. If they don't, then call
84 * logConflict() on the sensors that don't think the fan
87 * This check will only happen when power is on.
[all …]
|
| /openbmc/linux/arch/arm64/boot/dts/nvidia/ |
| H A D | tegra210-p2180.dtsi | 1 // SPDX-License-Identifier: GPL-2.0
2 #include <dt-bindings/mfd/max77620.h>
17 stdout-path = "serial0:115200n8";
26 vdd-supply = <&vdd_gpu>;
31 /delete-property/ dmas;
32 /delete-property/ dma-names;
45 vcc-supply = <&vdd_1v8>;
46 address-width = <8>;
49 read-only;
55 clock-frequency = <400000>;
[all …]
|
| H A D | tegra210-p3450-0000.dts | 1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
4 #include <dt-bindings/input/gpio-keys.h>
5 #include <dt-bindings/input/linux-event-codes.h>
6 #include <dt-bindings/mfd/max77620.h>
12 compatible = "nvidia,p3450-0000", "nvidia,tegra210";
22 stdout-path = "serial0:115200n8";
33 hvddio-pex-supply = <&vdd_1v8>;
34 dvddio-pex-supply = <&vdd_pex_1v05>;
35 vddio-pex-ctl-supply = <&vdd_1v8>;
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/display/panel/ |
| H A D | panel-edp.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/display/panel/panel-edp.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Douglas Anderson <dianders@chromium.org>
14 to a Embedded DisplayPort AUX bus (see display/dp-aux-bus.yaml) without
17 board, either for second-sourcing purposes or to support multiple SKUs
27 provided anywhere on the DP AUX bus is the power sequencing timings.
30 power on timings for any panels expected to be connected to a board are
31 specified in these bindings. Once we've powered on, it's expected that
[all …]
|
| H A D | samsung,s6e8aa0.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Andrzej Hajda <a.hajda@samsung.com>
13 - $ref: panel-common.yaml#
20 reset-gpios: true
21 display-timings: true
23 vdd3-supply:
26 vci-supply:
29 power-on-delay:
[all …]
|
| /openbmc/phosphor-fan-presence/docs/monitor/ |
| H A D | power_off_config.md | 5 A list of power off rules based on the monitoring state of the fans configured.
6 These power off rules can perform different system power off types to protect a
12 - `type` - ["hard", "soft", "epow"]
13 - "hard" - Perform a hard shutdown that immediately powers off the system.
14 - "soft" - Perform an orderly shutdown requesting that the host OS power off
16 - "epow" - Sets the thermal alert D-Bus property that a power off is imminent
18 - `cause` - ["missing_fan_frus", "nonfunc_fan_rotors"]
19 - "missing_fan_frus" - Power off due to missing fan enclosures
20 - "nonfunc_fan_rotors" - Power off due to nonfunctional fan
22 - "fan_frus_with_nonfunc_rotors" - Power off due to the number of fan FRUs
[all …]
|
| /openbmc/linux/include/linux/usb/ |
| H A D | isp1362.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
3 * board initialization code should put one of these into dev->platform_data
11 /* Enable internal pulldown resistors on downstream ports */
15 /* On-chip overcurrent protection */
29 /* Ganged port power switching (0) or individual port power switching (1) */
31 /* Given port_power, msec/2 after power on till power good */
37 /* Inter-io delay (ns). The chip is picky about access timings; it
39 * 110ns delay between consecutive accesses to DATA_REG,
40 * 300ns delay between access to ADDR_REG and DATA_REG (registers)
41 * 462ns delay between access to ADDR_REG and DATA_REG (buffer memory)
[all …]
|
| /openbmc/phosphor-state-manager/ |
| H A D | discover_system_state.cpp | 7 #include "xyz/openbmc_project/Control/Power/RestorePolicy/server.hpp"
10 #include <systemd/sd-bus.h>
12 #include <phosphor-logging/elog-errors.hpp>
13 #include <phosphor-logging/lg2.hpp>
36 using namespace sdbusplus::server::xyz::openbmc_project::control::power;
55 while ((arg = getopt_long(argc, argv, "h:", longOpts, &optIndex)) != -1) in main()
80 // This application is only run if chassis power is off in main()
83 // implement any power restore policies in main()
96 "BMC was reset due to pinhole reset, no power restore policy will be run"); in main()
102 "BMC was reset due to cold reset, no power restore policy will be run"); in main()
[all …]
|
| /openbmc/phosphor-fan-presence/monitor/ |
| H A D | power_off_action.hpp | 20 * This is the base class for a power off action, which is
22 * power offs based on fan failures.
24 * The power off is started with the start() method, and the
27 * there is a delay before the power off.
30 * the D-Bus call to do the power off, so it can be mocked
48 * @param[in] name - The action name. Used for tracing.
49 * @param[in] powerInterface - The object used to invoke the power off.
50 * @param[in] powerOffFunc - A function to call right before the power
63 * @brief Starts the power off.
72 * @brief Attempts to cancel the power off, if the derived
[all …]
|
| /openbmc/linux/Documentation/driver-api/usb/ |
| H A D | power-management.rst | 1 .. _usb-power-management:
3 Power Management for USB
7 :Date: Last-updated: February 2014
11 ---------
12 * What is Power Management?
17 * Changing the default idle-delay time
19 * The driver interface for Power Management
25 * USB Port Power Control
26 * User Interface for Port Power Control
27 * Suggested Userspace Port Power Policy
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Control/Power/ |
| H A D | RestorePolicy.interface.yaml | 2 Implement to specify power transition behavior on a BMC reset. The
3 implementation may choose to only enforce the policy on a power loss or on
4 both a power loss and BMC reboot.
7 - name: PowerRestorePolicy
12 - name: PowerRestoreDelay
16 The delay in microseconds before invoke power restore policy after
17 power applied. 0 - disable delay.
20 - name: Policy
22 Possible power restoration policies.
24 - name: None
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/regulator/ |
| H A D | fixed-regulator.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/regulator/fixed-regulator.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Liam Girdwood <lgirdwood@gmail.com>
11 - Mark Brown <broonie@kernel.org>
16 expected to have the regulator-min-microvolt and regulator-max-microvolt
20 - $ref: regulator.yaml#
21 - if:
25 const: regulator-fixed-clock
[all …]
|
| H A D | regulator-max77620.txt | 1 Regulator DT binding for MAX77620 Power management IC from Maxim Semiconductor.
3 Device has multiple DCDC(sd[0-3] and LDOs(ldo[0-8]). The input supply
6 sub-node "regulators" which is child node of device node.
14 -------------------
15 The input supply of regulators are the optional properties on the
18 in-sd0-supply: Input supply for SD0, INA-SD0 or INB-SD0 pins.
19 in-sd1-supply: Input supply for SD1.
20 in-sd2-supply: Input supply for SD2.
21 in-sd3-supply: Input supply for SD3.
22 in-ldo0-1-supply: Input supply for LDO0 and LDO1.
[all …]
|
| /openbmc/openbmc-test-automation/gui/gui_test/operations_menu/ |
| H A D | test_server_power_operations_sub_menu.robot | 3 Documentation Test OpenBMC GUI "Server power operations" sub-menu of "Operations".
8 Test Setup Run Keywords Launch Browser And Login GUI AND Navigate to Server Power Operation…
15 ${xpath_server_power_heading} //h1[text()="Server power operations"]
16 ${xpath_enable_onetime_boot_checkbox} //*[contains(@class,'custom-checkbox')]
17 ${xpath_boot_option_select} //*[@id='boot-option']
18 ${xpath_shutdown_button} //*[@data-test-id='serverPowerOperations-button-shutDown…
19 ${xpath_reboot_button} //*[@data-test-id='serverPowerOperations-button-reboot']
20 ${xpath_poweron_button} //*[@data-test-id='serverPowerOperations-button-powerOn']
22 ${xpath_shutdown_orderly_radio} //*[@data-test-id='serverPowerOperations-radio-shutdownO…
23 ${xpath_shutdown_immediate_radio} //*[@data-test-id='serverPowerOperations-radio-shutdownI…
[all …]
|
| /openbmc/linux/Documentation/power/ |
| H A D | runtime_pm.rst | 2 Runtime Power Management Framework for I/O Devices
5 (C) 2009-2011 Rafael J. Wysocki <rjw@sisk.pl>, Novell Inc.
14 Support for runtime power management (runtime PM) of I/O devices is provided
15 at the power management core (PM core) level by means of:
17 * The power management workqueue pm_wq in which bus types and device drivers can
18 put their PM-related work items. It is strongly recommended that pm_wq be
20 them to be synchronized with system-wide power transitions (suspend to RAM,
22 include/linux/pm_runtime.h and defined in kernel/power/main.c.
24 * A number of runtime PM fields in the 'power' member of 'struct device' (which
31 * A set of helper functions defined in drivers/base/power/runtime.c that can be
[all …]
|
| /openbmc/linux/arch/arm/boot/dts/mediatek/ |
| H A D | mt6323.dtsi | 1 // SPDX-License-Identifier: GPL-2.0
3 * Copyright (c) 2017-2018 MediaTek Inc.
12 interrupt-parent = <&pio>;
14 interrupt-controller;
15 #interrupt-cells = <2>;
18 compatible = "mediatek,mt6323-led";
19 #address-cells = <1>;
20 #size-cells = <0>;
25 compatible = "mediatek,mt6323-regulator";
28 regulator-name = "vproc";
[all …]
|
| /openbmc/linux/arch/arm/boot/dts/nxp/imx/ |
| H A D | imx6dl-mamoj.dts | 1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
7 /dts-v1/;
9 #include <dt-bindings/gpio/gpio.h>
14 compatible = "bticino,imx6dl-mamoj", "fsl,imx6dl";
22 backlight_lcd: backlight-lcd {
23 compatible = "pwm-backlight";
24 pwms = <&pwm3 0 25000>; /* 25000ns -> 40kHz */
25 brightness-levels = <0 4 8 16 32 64 128 160 192 224 255>;
26 default-brightness-level = <7>;
30 compatible = "fsl,imx-parallel-display";
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/mmc/ |
| H A D | mmc-pwrseq-simple.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/mmc/mmc-pwrseq-simple.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Simple MMC power sequence provider
10 - Ulf Hansson <ulf.hansson@linaro.org>
13 The purpose of the simple MMC power sequence provider is to supports a set
19 const: mmc-pwrseq-simple
21 reset-gpios:
27 at initialization and prior we start the power up procedure of the card.
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/pinctrl/ |
| H A D | pincfg-node.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/pinctrl/pincfg-node.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <linus.walleij@linaro.org>
21 bias-disable:
25 bias-high-impedance:
27 description: high impedance mode ("third-state", "floating")
29 bias-bus-hold:
33 bias-pull-up:
[all …]
|
| /openbmc/linux/drivers/gpu/drm/i915/display/ |
| H A D | intel_pps.c | 1 // SPDX-License-Identifier: MIT
31 switch (pps->pps_pipe) { in pps_name()
43 MISSING_CASE(pps->pps_pipe); in pps_name()
47 switch (pps->pps_idx) { in pps_name()
53 MISSING_CASE(pps->pps_idx); in pps_name()
67 * See intel_pps_reset_all() why we need a power domain reference here. in intel_pps_lock()
70 mutex_lock(&dev_priv->display.pps.mutex); in intel_pps_lock()
80 mutex_unlock(&dev_priv->display.pps.mutex); in intel_pps_unlock()
91 enum pipe pipe = intel_dp->pps.pps_pipe; in vlv_power_sequencer_kick()
97 if (drm_WARN(&dev_priv->drm, in vlv_power_sequencer_kick()
[all …]
|