Home
last modified time | relevance | path

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

12345678910>>...19

/openbmc/docs/designs/
H A Dpsu-monitoring.md1 # Power Supply Monitoring Application
7 Created: 2019-06-17
11 This is a proposal to provide a set of enhancements to the current OpenBMC power
13 may consist of a number of configuration variations including different power
15 different power supplies is needed in order to initialize the power supplies,
22 The OpenBMC project currently has a [witherspoon-pfault-analysis][1] repository
23 that contains a power supply monitor application and a power sequencer monitor
24 application. The current power supply application is lacking things desired for
28 a single power supply application that can communicate with one or more
29 [PMBus][2] power supplies and provide the enterprise features currently lacking
[all …]
H A Ddevice-tree-gpio-naming.md12 subsystem. The replacement is a "descriptor-based" character device interface.
25 specific field used to name the GPIOs in the DTS is `gpio-line-names`. This
29 scheme in the face of a universe of potential use-cases.
37 - Ensure common function GPIOs within OpenBMC use the same naming convention
52 Pattern: `*-button`
55 BMC-less machines use a button to trigger system behavior and in a BMC-managed
59 #### power-button
68 - `host*-ready`: Host ready, active high
69 - `host*-ready-n`: Host ready, active low
73 - host0-ready
[all …]
/openbmc/openbmc/meta-ibm/recipes-phosphor/dbus/power-supply-policy/
H A Dpower-supply-policy.yaml1 # Machine power supply policy for PDM.
3 # Create an error if a power supply is removed while the system is powered on
5 - name: power supply0
9 - meta: POWER SUPPLY
12 - name: power supply1
16 - meta: POWER SUPPLY
19 - name: power supplies
21 'The machine has two power supplies to monitor.'
25 - meta: POWER SUPPLY
27 - meta: POWER SUPPLY
[all …]
/openbmc/phosphor-power/phosphor-power-supply/
H A DREADME.md1 # OpenBMC power supply monitoring application
4 <https://github.com/openbmc/docs/blob/master/designs/psu-monitoring.md>
8 To enable reading VPD data via PMBus commands to IBM common form factor power
9 supplies (ibm-cffps), run meson with `-Dibm-vpd=true`.
11 ## D-Bus System Configuration
14 the power supply connectors (IBMCFFPSConnector).
18 ### Max Power Supplies
20 Integer that indicates the maximum number of power supplies that should be
25 The I2C bus(es) that the power supply is on will be represented by the `I2CBus`
31 The I2C address(es) that the power supply is at will be represented by the
[all …]
H A Dpsu_manager.hpp7 #include <phosphor-logging/log.hpp>
22 using namespace phosphor::power::psu;
25 namespace phosphor::power::manager namespace
33 // Validation timeout. Allow 30s to detect if new EM interfaces show up in D-Bus
54 * This class will create an object used to manage and monitor a list of power
68 * Constructor to read configuration from D-Bus.
70 * @param[in] bus - D-Bus bus object
71 * @param[in] e - event object
76 * Get PSU properties from D-Bus, use that to build a power supply
79 * @param[in] properties - A map of property names and values
[all …]
/openbmc/linux/drivers/hwmon/pmbus/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
31 tristate "ACBEL FSG032 Power Supply"
34 FSG032 Power Supply.
37 be called acbel-fsg032.
55 and ADM1294 Hot-Swap Controller and Digital Power Monitors.
61 tristate "Bel PFE Compatible Power Supplie
[all...]
/openbmc/linux/drivers/gpu/drm/panel/
H A Dpanel-startek-kd070fhfid015.c1 // SPDX-License-Identifier: GPL-2.0
8 * - Vinay Simha BN <simhavcs@gmail.com>
9 * - Sumit Semwal <sumit.semwal@linaro.org>
10 * - Guillaume La Roque <glaroque@baylibre.com>
34 POWER = 1 enumerator
42 struct gpio_desc *enable_gpio; /* Power IC supply enable */
45 struct regulator_bulk_data supplies[2]; member
55 struct mipi_dsi_device *dsi = stk->dsi; in stk_panel_init()
56 struct device *dev = &stk->dsi->dev; in stk_panel_init()
95 ret = mipi_dsi_dcs_set_column_address(dsi, 0, stk->mode->hdisplay - 1); in stk_panel_init()
[all …]
H A Dpanel-sony-td4353-jdi.c1 // SPDX-License-Identifier: GPL-2.0-only
5 * Generated with linux-mdss-dsi-panel-driver-generator with a
9 * - "JDI ID3" for Akari (XZ2)
10 * - "JDI ID4" for Apollo (XZ2 Compact)
28 * Leaving room for expansion - SONY very often uses
36 struct regulator_bulk_data supplies[3]; member
50 struct mipi_dsi_device *dsi = ctx->dsi; in sony_td4353_jdi_on()
51 struct device *dev = &dsi->dev; in sony_td4353_jdi_on()
54 dsi->mode_flags |= MIPI_DSI_MODE_LPM; in sony_td4353_jdi_on()
56 ret = mipi_dsi_dcs_set_column_address(dsi, 0x0000, 1080 - 1); in sony_td4353_jdi_on()
[all …]
/openbmc/linux/Documentation/devicetree/bindings/power/supply/
H A Dcpcap-battery.yaml1 # SPDX-License-Identifier: GPL-2.0
4 ---
5 $id: http://devicetree.org/schemas/power/supply/cpcap-battery.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Tony Lindgren <tony@atomide.com>
12 - Sebastian Reichel <sre@kernel.org>
17 sub-function.
20 - $ref: power-supply.yaml#
24 const: motorola,cpcap-battery
28 - description: eol interrupt
[all …]
/openbmc/linux/Documentation/driver-api/
H A Dregulator.rst1 .. Copyright 2007-2008 Wolfson Microelectronics
20 The intention is to allow systems to dynamically control regulator power
21 output in order to save power and prolong battery life. This applies to
27 ``Documentation/power/regulator``.
30 --------
36 Electronic device that supplies power to other devices. Most regulators
42 Electronic device which consumes power provided by a regulator. These
46 Power Domain
52 Power Management Integrated Circuit (PMIC)
62 drivers use `get <#API-regulator-get>`__ and
[all …]
/openbmc/linux/sound/soc/codecs/
H A Dwm8804.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * wm8804.c -- WM8804 S/PDIF transceiver driver
5 * Copyright 2010-11 Wolfson Microelectronics plc
26 #include <sound/soc-dapm.h>
37 { 3, 0x21 }, /* R3 - PLL1 */
38 { 4, 0xFD }, /* R4 - PLL2 */
39 { 5, 0x36 }, /* R5 - PLL3 */
40 { 6, 0x07 }, /* R6 - PLL4 */
41 { 7, 0x16 }, /* R7 - PLL5 */
42 { 8, 0x18 }, /* R8 - PLL6 */
[all …]
H A Dwm8523.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * wm8523.c -- WM8523 ALSA SoC Audio driver
40 struct regulator_bulk_data supplies[WM8523_NUM_SUPPLIES]; member
47 { 2, 0x0000 }, /* R2 - PSCTRL1 */
48 { 3, 0x1812 }, /* R3 - AIF_CTRL1 */
49 { 4, 0x0000 }, /* R4 - AIF_CTRL2 */
50 { 5, 0x0001 }, /* R5 - DAC_CTRL3 */
51 { 6, 0x0190 }, /* R6 - DAC_GAINL */
52 { 7, 0x0190 }, /* R7 - DAC_GAINR */
53 { 8, 0x0000 }, /* R8 - ZERO_DETECT */
[all …]
H A Dcs35l32.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * cs35l32.c -- CS35L32 ALSA SoC audio driver
27 #include <sound/soc-dapm.h>
30 #include <dt-bindings/sound/cs35l32.h>
44 struct regulator_bulk_data supplies[CS35L32_NUM_SUPPLIES]; member
51 { 0x06, 0x04 }, /* Power Ctl 1 */
52 { 0x07, 0xE8 }, /* Power Ctl 2 */
154 struct snd_soc_component *component = codec_dai->component; in cs35l32_set_dai_fmt()
167 return -EINVAL; in cs35l32_set_dai_fmt()
175 struct snd_soc_component *component = dai->component; in cs35l32_set_tristate()
[all …]
H A Dwm8782.c1 // SPDX-License-Identifier: GPL-2.0-or-later
4 * simple, strap-pin configured 24bit 2ch ADC
50 /* regulator power supply names */
52 "Vdda", /* analog supply, 2.7V - 3.6V */
53 "Vdd", /* digital supply, 2.7V - 5.5V */
57 struct regulator_bulk_data supplies[ARRAY_SIZE(supply_names)]; member
63 return regulator_bulk_enable(ARRAY_SIZE(priv->supplies), priv->supplies); in wm8782_soc_probe()
69 regulator_bulk_disable(ARRAY_SIZE(priv->supplies), priv->supplies); in wm8782_soc_remove()
76 regulator_bulk_disable(ARRAY_SIZE(priv->supplies), priv->supplies); in wm8782_soc_suspend()
83 return regulator_bulk_enable(ARRAY_SIZE(priv->supplies), priv->supplies); in wm8782_soc_resume()
[all …]
H A Dsta32x.c1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * Codec driver for ST STA32x 2.1-channel high-efficiency digital audio system
35 #include <sound/soc-dapm.h>
55 /* Power-up register defaults */
129 /* regulator power supply names */
133 "Vcc" /* power amp spply, 10V - 36V */
140 struct regulator_bulk_data supplies[ARRAY_SIZE(sta32x_supply_names)]; member
154 static const DECLARE_TLV_DB_SCALE(mvol_tlv, -12700, 50, 1);
155 static const DECLARE_TLV_DB_SCALE(chvol_tlv, -7950, 50, 1);
156 static const DECLARE_TLV_DB_SCALE(tone_tlv, -120, 200, 0);
[all …]
H A Dcs4270.c6 * Copyright 2007-2009 Freescale Semiconductor, Inc. This file is licensed
15 * - Software mode is supported. Stand-alone mode is not supported.
16 * - Only I2C is supported, not SPI
17 * - Support for master and slave mode
18 * - The machine driver's 'startup' function must call
20 * - Only I2S and left-justified modes are supported
21 * - Power management is supported
41 #define CS4270_PWRCTL 0x02 /* Power Control */
51 #define CS4270_NUMREGS (CS4270_LASTREG - CS4270_FIRSTREG + 1)
101 /* Power-on default values for the registers
[all …]
/openbmc/linux/drivers/mfd/
H A Dsi476x-i2c.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * drivers/mfd/si476x-i2c.c -- Core device driver for si476x MFD
21 #include <linux/mfd/si476x-core.h>
27 * si476x_core_config_pinmux() - pin function configuration function
39 dev_dbg(&core->client->dev, "Configuring pinmux\n"); in si476x_core_config_pinmux()
41 core->pinmux.dclk, in si476x_core_config_pinmux()
42 core->pinmux.dfs, in si476x_core_config_pinmux()
43 core->pinmux.dout, in si476x_core_config_pinmux()
44 core->pinmux.xout); in si476x_core_config_pinmux()
46 dev_err(&core->client->dev, in si476x_core_config_pinmux()
[all …]
/openbmc/linux/Documentation/devicetree/bindings/opp/
H A Dopp-v2-base.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/opp/opp-v2-base.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Viresh Kumar <viresh.kumar@linaro.org>
13 Devices work at voltage-current-frequency combinations and some implementations
25 pattern: '^opp-table(-[a-z0-9]+)?$'
27 opp-shared:
36 '^opp(-?[0-9]+)*$':
39 One or more OPP nodes describing voltage-current-frequency combinations.
[all …]
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-class-usb_power_delivery5 Directory for USB Power Delivery devices.
11 File showing the USB Power Delivery Specification Revision used
19 specific revision of the USB Power Delivery Specification. In
23 What: /sys/class/usb_power_delivery/.../source-capabilities
28 set of Power Data Objects (PDO), each representing a type of
29 power supply. The order of the PDO objects is defined in the USB
30 Power Delivery Specification. Each PDO - power supply - will
33 power supply type name (":" as delimiter).
37 What: /sys/class/usb_power_delivery/.../sink-capabilities
42 of Power Data Objects (PDO) just like with source capabilities,
[all …]
/openbmc/linux/Documentation/power/regulator/
H A Ddesign.rst9 ------
11 - Errors in regulator configuration can have very serious consequences
13 - It is not possible to automatically determine the power configuration
14 of the system - software-equivalent variants of the same chip may
15 have different power requirements, and not all components with power
25 ------------------
27 - The overwhelming majority of devices in a system will have no
28 requirement to do any runtime configuration of their power beyond
31 - Many of the power supplies in the system will be shared between many
38 supplies without any additional effort.
H A Doverview.rst11 The intention is to allow systems to dynamically control regulator power output
12 in order to save power and prolong battery life. This applies to both voltage
26 - Regulator
27 - Electronic device that supplies power to other devices.
31 Input Voltage -> Regulator -> Output Voltage
34 - PMIC
35 - Power Management IC. An IC that contains numerous
39 - Consumer
40 - Electronic device that is supplied power by a regulator.
41 Consumers can be classified into two types:-
[all …]
H A Dmachine.rst10 Regulator-1 -+-> Regulator-2 --> [Consumer A @ 1.8 - 2.0V]
12 +-> [Consumer B @ 3.3V]
15 order to control their power supplies. This mapping can be achieved in machine
21 const char *supply; /* consumer supply - e.g. "vcc" */
34 This maps Regulator-1 to the 'Vcc' supply for Consumer B and maps Regulator-2
38 for each regulator power domain. This structure also maps the consumers
43 .name = "Regulator-1",
53 for the board for configuration of supplies for other regulators and
58 Regulator-1 supplies power to Regulator-2. This relationship must be registered
59 with the core so that Regulator-1 is also enabled when Consumer A enables its
[all …]
/openbmc/linux/Documentation/devicetree/bindings/mfd/
H A Dcirrus,lochnagar.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - patches@opensource.cirrus.com
15 Logic devices on mini-cards, as well as allowing connection of
17 platform. Audio system topology, clocking and power can all be
25 [2] include/dt-bindings/pinctrl/lochnagar.h
26 [3] include/dt-bindings/clock/lochnagar.h
28 And these documents for the required sub-node binding details:
35 - if:
[all …]
/openbmc/linux/drivers/pci/controller/
H A Dpci-tegra.c1 // SPDX-License-Identifier: GPL-2.0+
9 * Copyright (c) 2008-2009, NVIDIA Corporation.
11 * Bits taken from arch/arm/mach-dove/pcie.c
256 * Fields in PADS_REFCLK_CFG*. Those registers form an array of 16-bit
349 struct regulator_bulk_data *supplies; member
378 writel(value, pcie->afi + offset); in afi_writel()
383 return readl(pcie->afi + offset); in afi_readl()
389 writel(value, pcie->pads + offset); in pads_writel()
394 return readl(pcie->pads + offset); in pads_readl()
429 struct tegra_pcie *pcie = bus->sysdata; in tegra_pcie_map_bus()
[all …]
/openbmc/openbmc-test-automation/redfish/systems/
H A Dtest_systems_inventory.robot75 [Documentation] Check that the System SerialNumber is non-blank.
84 [Documentation] Check that the Model is non-blank.
92 Get Available Power Supplies And Verify
93 [Documentation] Get the number of functional power supplies and
97 # Select only power supplies with Health = "OK".
100 # Count the power supplies that are Enabled or StandbyOffline.
104 # power_supply = {'@odata.id': '/redfish/v1/Chassis/chassis/Power#/PowerSupplies/0',
121 [Documentation] Check that the Motherboard SerialNumber is non-blank.
130 [Documentation] Check that the Motherboard manufacturer is non-blank.
139 [Documentation] Check that the Motherboard partnumber is non-blank.
[all …]

12345678910>>...19