| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Control/ |
| H A D | Failover.interface.yaml | 15 Identifies who's requesting the failover 28 Who is requesting the failover. 32 The host is requesting the failover. 35 A Redfish client is requesting the failover. 38 A system config checker on the BMC is requesting the failover. 41 A command line tool is requesting the failover.
|
| /openbmc/phosphor-buttons/src/ |
| H A D | host_then_chassis_poweroff.cpp | 134 lg2::info("Power button action requesting host transition of {TRANS}", in hostTransition() 146 lg2::error("Failed requesting host transition {TRANS}: {ERROR}", in hostTransition() 163 lg2::info("Power button action requesting chassis power off"); in chassisPowerOff() 180 lg2::error("Failed requesting chassis off: {ERROR}", "ERROR", e); in chassisPowerOff()
|
| /openbmc/phosphor-host-ipmid/ |
| H A D | host-cmd-manager.hpp | 90 * or from a user doing something like requesting an already 92 * requesting a power on.
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Logging/ |
| H A D | IPMI.interface.yaml | 42 The Generator ID of the component requesting the new SEL entry. 72 The Generator ID of the component requesting the new SEL entry.
|
| /openbmc/openpower-hw-diags/ |
| H A D | meson.options | 20 description: 'Object path requesting OpenPOWER dumps',
|
| H A D | config.h.in | 23 // D-Bus path for requesting dumps
|
| /openbmc/openpower-occ-control/ |
| H A D | meson.options | 31 description: 'Object path requesting OpenPOWER dumps',
|
| /openbmc/webui-vue/.github/ISSUE_TEMPLATE/ |
| H A D | design-review.md | 26 - Any description or specific feedback the designer is requesting
|
| /openbmc/ipmitool/lib/ |
| H A D | ipmi_sol.c | 219 lprintf(LOG_ERR, "Error: No response requesting SOL parameter '%s'", in ipmi_get_sol_info() 240 lprintf(LOG_ERR, "Error requesting SOL parameter '%s': %s", in ipmi_get_sol_info() 257 lprintf(LOG_ERR, "Error: No response requesting SOL parameter '%s'", in ipmi_get_sol_info() 278 lprintf(LOG_ERR, "Error requesting SOL parameter '%s': %s", in ipmi_get_sol_info() 295 lprintf(LOG_ERR, "Error: No response requesting SOL parameter '%s'", in ipmi_get_sol_info() 318 lprintf(LOG_ERR, "Error requesting SOL parameter '%s': %s", in ipmi_get_sol_info() 335 lprintf(LOG_ERR, "Error: No response requesting SOL parameter '%s'", in ipmi_get_sol_info() 357 lprintf(LOG_ERR, "Error requesting SOL parameter '%s': %s", in ipmi_get_sol_info() 374 lprintf(LOG_ERR, "Error: No response requesting SOL parameter '%s'", in ipmi_get_sol_info() 396 lprintf(LOG_ERR, "Error requesting SOL parameter '%s': %s", in ipmi_get_sol_info() [all …]
|
| /openbmc/qemu/tests/functional/ |
| H A D | test_s390x_tuxrun.py | 32 haltmsg="Requesting system halt")
|
| /openbmc/openpower-hw-diags/attn/ |
| H A D | Attention_Handler.md | 54 - dbus: querying the state of the BMC and host, requesting dumps and requesting 150 call the analyzer before requesting a dump or IPL. The check for recoverable
|
| /openbmc/openpower-proc-control/ |
| H A D | meson.options | 47 description: 'Object path requesting OpenPOWER dumps',
|
| /openbmc/qemu/tests/qtest/ |
| H A D | lsm303dlhc-mag-test.c | 118 /* Check that requesting 4 bytes starting at Y_H wraps around to X_L */ in reg_wraparound() 127 /* Check that requesting LSM303DLHC_MAG_REG_IRC wraps around to CRA */ in reg_wraparound()
|
| H A D | tpm-tis-util.c | 140 * requesting use from 'l' was not possible; in tpm_tis_test_check_access_reg_seize() 193 * requesting use from 'l' was not possible; we should see in tpm_tis_test_check_access_reg_seize() 205 * see PENDING_REQUEST from 'l' requesting access in tpm_tis_test_check_access_reg_seize()
|
| /openbmc/docs/ |
| H A D | discord-rules.md | 21 you are requesting. If you are new to the community, you will likely have the
|
| /openbmc/openbmc/meta-google/recipes-google/networking/gbmc-bridge/ |
| H A D | 50-gbmc-psu-hardreset.sh.in | 40 update_netboot_status "pwr_req" "Requesting powercycle" "SUCCESS"
|
| /openbmc/u-boot/drivers/misc/ |
| H A D | gpio_led.c | 35 printf("%s: failed requesting GPIO%lu!\n", __func__, mask); in __led_init()
|
| /openbmc/phosphor-bmc-code-mgmt/eeprom-device/ |
| H A D | eeprom_device.cpp | 68 debug("Requesting chip {CHIP}, GPIO line {LINE} to {VALUE}", "CHIP", in requestMuxGPIOs() 155 debug("Requesting GPIOs to mux EEPROM to BMC"); in updateDevice() 201 debug("Requesting GPIOs to mux EEPROM back to device"); in updateDevice()
|
| /openbmc/qemu/nbd/ |
| H A D | trace-events | 17 nbd_opt_meta_request(const char *optname, const char *context, const char *export) "Requesting %s %… 22 nbd_receive_negotiate_name(const char *name) "Requesting NBD export name '%s'"
|
| /openbmc/phosphor-fan-presence/docs/monitor/ |
| H A D | power_off_config.md | 14 - "soft" - Perform an orderly shutdown requesting that the host OS power off
|
| /openbmc/bmcweb/include/ |
| H A D | forward_unauthorized.hpp | 54 // doing their requests, even though they might not be requesting html. in sendUnauthorized()
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | CompositionService.v1_2_3.json | 218 …he active pool. Services shall filter members of this collection based on the requesting client.", 245 …e reservations. Services shall filter members of this collection based on the requesting client.", 263 … the free pool. Services shall filter members of this collection based on the requesting client.",
|
| /openbmc/dbus-sensors/src/adc/ |
| H A D | ADCSensor.hpp | 46 lg2::error("Error requesting gpio: '{NAME}'", "NAME", name); in BridgeGpio()
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | SMPPL | 17 …y you and/or by others) upon request, or instead you may notify anyone requesting the SMP Software…
|
| /openbmc/u-boot/include/asm-generic/ |
| H A D | gpio.h | 418 * tree property) and requesting the GPIO for use. The property must exist 427 * If we find that requesting the GPIO is not always needed we could add a 441 * @dev: Device requesting the GPIO 467 * @dev: Device requesting the GPIO 497 * @dev: Device requesting the GPIO
|