/openbmc/phosphor-power/phosphor-power-sequencer/docs/ |
H A D | powering_on.md | 1 # Powering On 13 The `phosphor-power-sequencer` application only supports powering on the entire 15 support powering on individual chassis independent of the rest of the system. 41 ## Powering on the voltage rails 77 When the power sequencer device is powering on the main voltage rails, one of
|
H A D | powering_off.md | 1 # Powering Off 13 The `phosphor-power-sequencer` application only supports powering off the entire 15 support powering off individual chassis independent of the rest of the system. 36 ## Powering off the voltage rails
|
H A D | README.md | 48 ## Powering on the system 53 See [Powering On](powering_on.md) for more information. 55 ## Powering off the system 60 See [Powering Off](powering_off.md) for more information.
|
H A D | pgood_faults.md | 11 ## Pgood fault while powering on the system 13 When the power sequencer device is powering on the main voltage rails in order, 40 - Powering on chassis: pgood signal never changes to true.
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Item/ |
H A D | PowerSupply.interface.yaml | 5 - name: powering 8 'powering' association to provide a link back to a Item.
|
H A D | README.md | 26 - PowerSupply and Item: `{powering, powered_by}`
|
H A D | Chassis.interface.yaml | 59 reverse_name: powering
|
/openbmc/qemu/target/arm/ |
H A D | arm-powerctl.c | 120 /* Retrieve the cpu we are powering up */ in arm_set_cpu_on() 168 "[ARM]%s: CPU %" PRId64 " is already powering on\n", in arm_set_cpu_on() 211 /* Retrieve the cpu we are powering up */ in arm_set_cpu_on_and_reset() 234 "[ARM]%s: CPU %" PRId64 " is already powering on\n", in arm_set_cpu_on_and_reset() 266 /* change to the cpu we are powering up */ in arm_set_cpu_off()
|
H A D | arm-powerctl.h | 47 * QEMU_ARM_POWERCTL_ON_PENDING if the CPU is still powering up 89 * powering on.
|
/openbmc/openbmc/meta-facebook/meta-tiogapass/recipes-tiogapass/fb-powerctrl/files/ |
H A D | power-util | 14 echo "Powering on Server" 67 echo "WARNING: Powering on server"
|
/openbmc/phosphor-power/phosphor-regulators/docs/ |
H A D | multiple_chassis.md | 17 `phosphor-regulators` only supports powering on and off the entire system. It 18 does not support powering on/off individual chassis independent of the rest of
|
/openbmc/bmcweb/redfish-core/include/registries/ |
H A D | resource_event_message_registry.hpp | 205 "Indicates that the power state of a resource has changed to powering off.", 206 "The resource `%1` is powering off.", 217 "Indicates that the power state of a resource has changed to powering on.", 218 "The resource `%1` is powering on.",
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Software/ |
H A D | Version.errors.yaml | 7 prevented from powering on if a minimum version level is not met.
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Decorator/ |
H A D | MeetsMinimumShipLevel.interface.yaml | 8 system from powering on or logging events.'
|
/openbmc/openbmc/meta-fii/meta-kudo/recipes-kudo/host/files/ |
H A D | ampere_power_util.sh | 17 echo "Powering down Server" 30 echo "Powering on Server"
|
/openbmc/u-boot/include/linux/usb/ |
H A D | at91_udc.h | 10 int vbus_pin; /* high == host powering us */
|
/openbmc/phosphor-fan-presence/docs/monitor/ |
H A D | monitor_start_delay.md | 6 powering on the system. This attribute is optional and defaults to 0, meaning
|
/openbmc/entity-manager/test/ |
H A D | test_topology.cpp | 18 std::make_tuple("powering", "powered_by", superchassisPath); 358 "PortType": "powering", in TEST() 380 // configure the PSUs to be powering something in TEST() 399 // expect powering association from each PSU to the board in TEST() 403 assocs[psu0Path].contains({"powering", "powered_by", boardPath})); in TEST() 409 assocs[psu1Path].contains({"powering", "powered_by", boardPath})); in TEST()
|
/openbmc/entity-manager/src/entity_manager/ |
H A D | topology.cpp | 10 // Topology tests say that a chassis can be powering another chassis. 11 // In case there is any confusion as to why 'Chassis' can have 'powering' 14 AssocName("powering", "powered_by", {"Chassis", "PowerSupply"},
|
/openbmc/openbmc/meta-google/recipes-google/host-power-ctrl/gpio-host-pwr/ |
H A D | host_ensure_off.sh | 21 echo "Powering off the host" >&2
|
/openbmc/openpower-proc-control/ |
H A D | util.hpp | 26 * @return bool - true if host is powering off else false. if failed
|
/openbmc/phosphor-power/phosphor-power-sequencer/src/ |
H A D | power_control.cpp | 154 // Time out powering on in pollPgood() 159 // Time out powering off in pollPgood() 226 // Wait for two seconds when powering down. This is to allow host and in setState() 245 services.logInfoMsg(std::format("Powering chassis {}", (s ? "on" : "off"))); in setState()
|
/openbmc/openpower-proc-control/procedures/phal/ |
H A D | set_SPI_mux.cpp | 32 * masters. This should only be executed before the host is powering on since
|
/openbmc/openbmc-test-automation/openpower/ |
H A D | test_timed_power_on.robot | 65 # system is powering on. Though we have set system to power on in 100 seconds 95 # system is powering on after user timer set and delta time to update BootProgress
|
/openbmc/openbmc/meta-facebook/meta-yosemite4/recipes-phosphor/dbus/phosphor-dbus-monitor/ |
H A D | fan-rotor-fail-mechanism | 23 echo "Powering off slot $slot_number..."
|