Home
last modified time | relevance | path

Searched refs:power (Results 1 – 25 of 1779) sorted by relevance

12345678910>>...72

/openbmc/u-boot/arch/arm/mach-exynos/
H A Dpower.c41 struct exynos5_power *power = in exynos5_set_usbhost_phy_ctrl() local
46 setbits_le32(&power->usbhost_phy_control, in exynos5_set_usbhost_phy_ctrl()
50 clrbits_le32(&power->usbhost_phy_control, in exynos5_set_usbhost_phy_ctrl()
57 struct exynos4412_power *power = in exynos4412_set_usbhost_phy_ctrl() local
62 setbits_le32(&power->usbhost_phy_control, in exynos4412_set_usbhost_phy_ctrl()
64 setbits_le32(&power->hsic1_phy_control, in exynos4412_set_usbhost_phy_ctrl()
66 setbits_le32(&power->hsic2_phy_control, in exynos4412_set_usbhost_phy_ctrl()
70 clrbits_le32(&power->usbhost_phy_control, in exynos4412_set_usbhost_phy_ctrl()
72 clrbits_le32(&power->hsic1_phy_control, in exynos4412_set_usbhost_phy_ctrl()
74 clrbits_le32(&power->hsic2_phy_control, in exynos4412_set_usbhost_phy_ctrl()
[all …]
/openbmc/u-boot/arch/powerpc/dts/
H A De6500_power_isa.dtsi11 power-isa-version = "2.06";
12 power-isa-b; // Base
13 power-isa-e; // Embedded
14 power-isa-atb; // Alternate Time Base
15 power-isa-cs; // Cache Specification
16 power-isa-ds; // Decorated Storage
17 power-isa-e.ed; // Embedded.Enhanced Debug
18 power-isa-e.pd; // Embedded.External PID
19 power-isa-e.hv; // Embedded.Hypervisor
20 power-isa-e.le; // Embedded.Little-Endian
[all …]
/openbmc/openbmc/meta-ampere/meta-mitchell/recipes-phosphor/configuration/mtmitchell-yaml-config/
H A Dmtmitchell-ipmi-sensors.yaml430 123: &power
477 <<: *power
586 <<: *power
613 <<: *power
638 <<: *power
663 <<: *power
689 <<: *power
715 <<: *power
741 <<: *power
766 <<: *power
[all …]
/openbmc/u-boot/arch/arm/dts/
H A Dbcm2835-rpi.dtsi1 #include <dt-bindings/power/raspberrypi-power.h>
25 power: power { label
26 compatible = "raspberrypi,bcm2835-power";
28 #power-domain-cells = <1>;
85 power-domains = <&power RPI_POWER_DOMAIN_USB>;
89 power-domains = <&power RPI_POWER_DOMAIN_V3D>;
93 power-domains = <&power RPI_POWER_DOMAIN_HDMI>;
98 power-domains = <&power RPI_POWER_DOMAIN_VEC>;
103 power-domains = <&power RPI_POWER_DOMAIN_DSI0>;
107 power-domains = <&power RPI_POWER_DOMAIN_DSI1>;
H A Dfsl-imx8dx.dtsi126 #power-domain-cells = <0>;
132 #power-domain-cells = <0>;
133 power-domains = <&pd_lsio>;
137 #power-domain-cells = <0>;
138 power-domains = <&pd_lsio>;
142 #power-domain-cells = <0>;
143 power-domains = <&pd_lsio>;
147 #power-domain-cells = <0>;
148 power-domains = <&pd_lsio>;
152 #power-domain-cells = <0>;
[all …]
/openbmc/openbmc/meta-ampere/meta-jade/recipes-phosphor/configuration/mtjade-yaml-config/
H A Dmtjade-ipmi-sensors.yaml347 112: &power
367 <<: *power
372 <<: *power
377 <<: *power
424 <<: *power
429 <<: *power
434 <<: *power
439 <<: *power
479 <<: *power
496 <<: *power
[all …]
/openbmc/openbmc/meta-ingrasys/meta-zaius/recipes-phosphor/configuration/zaius-yaml-config/
H A Dzaius-ipmi-sensors.yaml216 0x74: &power
259 <<: *power
271 <<: *power
283 <<: *power
295 <<: *power
307 <<: *power
316 <<: *power
328 <<: *power
340 <<: *power
352 <<: *power
[all …]
/openbmc/docs/designs/
H A Dpsu-monitoring.md11 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,
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
31 power supply.
38 1. The power supply application must detect, isolate, and report individual
39 input power and power FRU faults, during boot and at runtime only.
[all …]
H A Dpower-recovery.md11 Modern computer systems have a feature, automated power-on recovery, which in
13 power to the system. If the system had a black out (i.e. power was completely
14 cut to the system), should it automatically power the system on? Should it leave
16 at before the power loss.
18 There are also instances where the user may not want automatic power recovery to
22 situations, the user may wish for the system to not automatically power on the
26 run once the power is restored. For example, IBM requires all LED's be toggled
30 A brownout is another scenario that commonly utilizes automated power-on
32 told) that chassis power can no longer be supported, but power to the BMC will
33 be retained. On some systems, it's desired to utilize the automated power-on
[all …]
/openbmc/u-boot/drivers/power/domain/
H A DKconfig4 bool "Enable power domain support using Driver Model"
7 Enable support for the power domain driver class. Many SoCs allow
8 power to be applied to or removed from portions of the SoC (power
9 domains). This may be used to save power. This API provides the
10 means to control such power management hardware.
13 bool "Enable the BCM6328 power domain driver"
16 Enable support for manipulating BCM6345 power domains via MMIO
20 bool "Enable i.MX8 power domain driver"
23 Enable support for manipulating NXP i.MX8 on-SoC power domains via IPC
27 bool "Enable the MediaTek power domain driver"
[all …]
H A DMakefile6 obj-$(CONFIG_$(SPL_)POWER_DOMAIN) += power-domain-uclass.o
7 obj-$(CONFIG_BCM6328_POWER_DOMAIN) += bcm6328-power-domain.o
8 obj-$(CONFIG_IMX8_POWER_DOMAIN) += imx8-power-domain.o
9 obj-$(CONFIG_MTK_POWER_DOMAIN) += mtk-power-domain.o
11 obj-$(CONFIG_SANDBOX_POWER_DOMAIN) += sandbox-power-domain.o
12 obj-$(CONFIG_SANDBOX_POWER_DOMAIN) += sandbox-power-domain-test.o
13 obj-$(CONFIG_TEGRA186_POWER_DOMAIN) += tegra186-power-domain.o
14 obj-$(CONFIG_TI_SCI_POWER_DOMAIN) += ti-sci-power-domain.o
/openbmc/openbmc-test-automation/redfish/extended/
H A Dtest_power_capping.robot2 Documentation Energy scale power capping tests.
35 [Documentation] Change active power limit with system power on and
67 ${power}= Get DCMI Power Limit
68 Should Be True ${power} == ${max_power}
69 ... msg=DCMI power limit should be ${max_power}.
77 [Documentation] Change active power limit with system power on and
78 ... deactivate power limit prior to change.
90 ${cmd}= Catenate dcmi power set_limit limit ${near_max_power_50}
92 ${power}= Get DCMI Power Limit
94 Should Be True ${power} == ${near_max_power_50}
[all …]
/openbmc/openbmc/meta-quanta/meta-olympus-nuvoton/recipes-phosphor/configuration/olympus-nuvoton-yaml-config/
H A Dolympus-nuvoton-ipmi-sensors.yaml139 23: &power
161 <<: *power
165 <<: *power
169 <<: *power
173 <<: *power
177 <<: *power
181 <<: *power
185 <<: *power
189 <<: *power
469 <<: *power
[all …]
/openbmc/phosphor-power/phosphor-power-sequencer/docs/
H A DREADME.md1 # phosphor-power-sequencer
5 The `phosphor-power-sequencer` application powers all the chassis in the system
6 on and off. It also monitors the power good (pgood) state in each chassis.
12 `phosphor-chassis-power` application. This disclaimer will be removed when this
17 `phosphor-power-sequencer` is a single-threaded C++ executable. It is a daemon
21 `phosphor-power-sequencer` is driven by an optional, system-specific JSON
24 chassis, power sequencer devices, voltage rails, GPIOs, and fault checks to
31 A power sequencer device enables (turns on) the voltage rails in the correct
34 `phosphor-power-sequencer` currently supports the following power sequencer
44 If the power sequencer device type is not supported, `phosphor-power-sequencer`
[all …]
H A Dpowering_on.md3 ## Initiating a power on
6 Redfish command, or a power button on the system enclosure.
13 The `phosphor-power-sequencer` application only supports powering on the entire
14 system. In a multiple chassis system, `phosphor-power-sequencer` does not
17 ## Determining which chassis to power on
19 In a single chassis system, `phosphor-power-sequencer` will always attempt to
20 power on the chassis.
22 In a multiple chassis system, `phosphor-power-sequencer` will only attempt to
23 power on chassis with the proper status:
30 `phosphor-power-sequencer` will set the `state` property to 1 for each chassis
[all …]
H A Dpowering_off.md3 ## Initiating a power off
6 Redfish command, or a power button on the system enclosure.
13 The `phosphor-power-sequencer` application only supports powering off the entire
14 system. In a multiple chassis system, `phosphor-power-sequencer` does not
17 ## Determining which chassis to power off
19 In a single chassis system, `phosphor-power-sequencer` will always attempt to
20 power off the chassis.
22 In a multiple chassis system, `phosphor-power-sequencer` will only attempt to
23 power off chassis with the proper status:
28 `phosphor-power-sequencer` will set the `state` property to 0 for all chassis.
[all …]
H A Dmonitoring_chassis_pgood.md5 The power sequencer device provides a chassis power good (pgood) signal. This
8 The `phosphor-power-sequencer` application periodically reads (polls) the
16 If the chassis pgood state is false when it should be true, a chassis power good
20 ## Unable to read chassis power good signal
22 `phosphor-power-sequencer` may become unable to read the chassis power good
29 ### During power on
31 If `phosphor-power-sequencer` is unable to read the chassis power good signal
32 during a power on attempt, the application will do the following:
35 - Log an error specifying the power on attempt failed due to an inability to
36 read the chassis power good status.
[all …]
H A Dpgood_faults.md5 The power sequencer device provides a chassis power good (pgood) signal. This
8 If the chassis pgood state is false when it should be true, a chassis power good
13 When the power sequencer device is powering on the main voltage rails in order,
14 one of the rails may fail to power on. This is often due to a hardware problem.
16 When a voltage rail fails to power on, the power sequencer device may
18 for the rail to power on. In both cases the chassis pgood signal never changes
26 A voltage rail may suddenly power off or stop providing the expected level of
30 The power sequencer device will detect that the voltage rail has failed. The
32 may also power off several other related voltage rails, depending on how the
37 `phosphor-power-sequencer` detects a pgood fault by monitoring the chassis pgood
[all …]
/openbmc/openbmc/meta-facebook/meta-santabarbara/recipes-phosphor/state/phosphor-state-manager/
H A Dchassis-powercycle4 source /usr/libexec/phosphor-state-manager/power-cmd
12 chassis-power-cycle-ltc4287() {
45 chassis-power-cycle-xdp711() {
63 chassis-power-cycle()
67 chassis-power-cycle-ltc4287
71 chassis-power-cycle-xdp711
85 iris-power-cycle() {
98 chassis-power-cycle
103 iris-power-cycle $((ChassisNumber - 1))
/openbmc/openbmc-test-automation/lib/
H A Denergy_scale_utils.robot2 Documentation Utilities for power management tests.
17 [Documentation] Get the allowed MAX and MIN power limit of the chassis.
33 [Documentation] Run dcmi power get_limit and return values as a
36 # This keyword packages the five lines returned by dcmi power get_limit
43 # The power limit setting can be obtained with the following:
47 ${output}= Run External IPMI Standard Command dcmi power get_limit
65 [Documentation] Set system power limit via IPMI DCMI command.
69 # limit The power limit in watts
71 ${cmd}= Catenate dcmi power set_limit limit ${power_limit}
73 ${power}= Get DCMI Power Limit
[all …]
/openbmc/phosphor-state-manager/service_files/
H A Dobmc-power-stop@.service3 Wants=obmc-power-stop@%i.target
4 Before=obmc-power-stop@%i.target
5 Wants=obmc-power-stop-pre@%i.target
6 After=obmc-power-stop-pre@%i.target
7 Wants=mapper-wait@-org-openbmc-control-power%i.service
8 After=mapper-wait@-org-openbmc-control-power%i.service
13 …h -c "busctl call `mapper get-service /org/openbmc/control/power%i` /org/openbmc/control/power%i o…
14 SyslogIdentifier=obmc-power-stop
H A Dobmc-power-start@.service3 Wants=obmc-power-start@%i.target
4 Before=obmc-power-start@%i.target
5 Wants=obmc-power-start-pre@%i.target
6 After=obmc-power-start-pre@%i.target
8 Wants=mapper-wait@-org-openbmc-control-power%i.service
9 After=mapper-wait@-org-openbmc-control-power%i.service
16 …h -c "busctl call `mapper get-service /org/openbmc/control/power%i` /org/openbmc/control/power%i o…
17 SyslogIdentifier=phosphor-power-start
/openbmc/openbmc/meta-hpe/meta-rl300-g11/recipes-hpe/power-sequencing/
H A Dpower-sequencing.bb4 SYSTEMD_SERVICE:${PN} = "monitor-ipmi-power-transition.service power-sequencing.service gpiosdown.s…
5 …power-transition.service file://ipmi-power-button-monitoring.sh file://rl300Start.sh file://power-…
11 IMAGE_INSTALL += "power-sequencing "
20 …install -m 0644 ${UNPACKDIR}/power-sequencing.service ${D}${sysconfdir}/system/power-sequencing.se…
25 …install -m 0644 ${UNPACKDIR}/monitor-ipmi-power-transition.service ${D}${sysconfdir}/system/monito…
29 …install -m 0755 ${UNPACKDIR}/ipmi-power-button-monitoring.sh ${D}/usr/bin/ipmi-power-button-monito…
30 install -m 0755 ${UNPACKDIR}/power-button.sh ${D}/usr/bin/power-button.sh
/openbmc/openbmc/meta-hpe/meta-dl360-g11/recipes-hpe/power-sequencing/
H A Dpower-sequencing.bb4 SYSTEMD_SERVICE:${PN} = "monitor-ipmi-power-transition.service power-sequencing.service gpiosdown.s…
5 …power-transition.service file://ipmi-power-button-monitoring.sh file://dl360Start.sh file://power-…
11 IMAGE_INSTALL += "power-sequencing "
20 …install -m 0644 ${UNPACKDIR}/power-sequencing.service ${D}${sysconfdir}/system/power-sequencing.se…
25 …install -m 0644 ${UNPACKDIR}/monitor-ipmi-power-transition.service ${D}${sysconfdir}/system/monito…
29 …install -m 0755 ${UNPACKDIR}/ipmi-power-button-monitoring.sh ${D}/usr/bin/ipmi-power-button-monito…
30 install -m 0755 ${UNPACKDIR}/power-button.sh ${D}/usr/bin/power-button.sh
/openbmc/phosphor-fan-presence/docs/monitor/
H A Dpower_off_config.md5 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
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
25 - Number of the configured `cause` instances to begin the power off `type`
27 ### "hard" & "soft" `type` power offs
30 - Time(in seconds) to delay performing the power off after `count` instances
33 - `at_pgood` - At system pgood, the power off rule becomes valid. A power off
34 rule of `at_pgood` can halt a system power on if the conditions are met.
35 - `runtime` - At system runtime, the power off rule becomes valid. A power off
[all …]

12345678910>>...72