| /openbmc/openbmc/meta-phosphor/recipes-phosphor/state/ |
| H A D | phosphor-state-manager-systemd-links.inc | 2 multi-user.target.wants/obmc-host-reset@{}.target \ 3 multi-user.target.wants/phosphor-discover-system-state@{}.service \ 4 obmc-host-start@{}.target.requires/obmc-host-startmin@{}.target \ 5 obmc-host-start@{}.target.requires/phosphor-reset-host-reboot-attempts@{}.service \ 6 obmc-host-startmin@{}.target.wants/phosphor-set-host-transition-to-running@{}.service \ 7 obmc-host-stop@{}.target.wants/phosphor-set-host-transition-to-off@{}.service \ 8 obmc-host-reset@{}.target.requires/phosphor-reset-host-running@{}.service \ 9 obmc-host-stop@{}.target.wants/phosphor-reset-sensor-states@{}.service \ 10 obmc-host-shutdown@{}.target.requires/obmc-host-stop@{}.target \ 11 obmc-host-graceful-quiesce@{}.target.wants/obmc-host-quiesce@{}.target \ [all …]
|
| /openbmc/openbmc/meta-facebook/meta-yosemite5/recipes-phosphor/gpio/ |
| H A D | phosphor-gpio-monitor_%.bbappend | 3 inherit obmc-phosphor-systemd systemd 5 SRC_URI += "file://yosemite5-phosphor-multi-gpio-monitor.json \ 8 file://multi-gpios-sys-init \ 9 file://multi-gpios-sys-init.service \ 10 file://assert-host-ready.service \ 11 file://deassert-host-ready.service \ 12 file://assert-power-good-drop \ 13 file://assert-power-good-drop.service \ 14 file://deassert-power-good-drop \ 15 file://deassert-power-good-drop.service \ [all …]
|
| /openbmc/docs/designs/ |
| H A D | multihost-ipmi-design.md | 1 # Multi-host IPMI design 12 The current version of OpenBMC does not support multi-host implementation in 13 IPMI commands handling. We have a multi-host system and proposing the design to 14 support multi-host. 16 As detailed below the hosts are connected in the IPMB interface, all host 22 The ipmid handlers should have the host details to fetch the host specific 30 +------------------------------------+ 32 | +-----------+ +------------+ | +--------+ 34 | | | | |-|------| Host-1 | 36 | | | | | | +--------+ [all …]
|
| H A D | multi-host-postcode.md | 1 # Multi-host Postcode Support 7 Created: 2020-07-02 11 The current implementation in the phosphor-host-postd supports only single host 14 As the open BMC architecture is evolving, the single host support becomes 15 contingent and needs multiple-host post code access to be implemented. 19 The below component diagram shows the design for single-host postcode and 20 history at high-level overview. The single-host design is updated slightly from 22 D-Bus objects). 24 Diagram Legend: |Label|Signifies| |-----|---------| |`I:` |D-Bus interface| 25 |`S:` |D-Bus service name (well-known bus name)| |`R:` |Repository name| |`U:` [all …]
|
| /openbmc/phosphor-buttons/inc/ |
| H A D | button_handler.hpp | 45 * There are 3 buttons supported - Power, ID, and Reset. 47 * check for that button on D-Bus before listening for its signals. 62 * @param[in] bus - sdbusplus connection object 72 * @param[in] msg - sdbusplus message from signal 81 * @param[in] msg - sdbusplus message from signal 88 * Reboots the host if it is powered on. 90 * @param[in] msg - sdbusplus message from signal 95 * @brief The handler for a OCP debug card host selector button press 97 * In multi host system increases host position by 1 up to max host 100 * @param[in] msg - sdbusplus message from signal [all …]
|
| /openbmc/phosphor-buttons/ |
| H A D | README.md | 1 # phosphor-buttons 3 Phosphor-buttons has a collection of IO event handler interfaces for physical 8 its associated IO for event changes and emits signals that the button-handler 17 If the power is off, power on the host. 22 - Short press: Do a host power off 23 - Long press, as determined by the 'long-press-time-ms' meson option: Do a 28 The 'power-button-profile' meson option can be used to select custom power 33 - host_then_chassis_poweroff: When power is on, short presses are ignored and a 34 long press issues a host power off first and then a chassis power off if held 38 ### Multi-Host Buttons [all …]
|
| /openbmc/openbmc/meta-ampere/meta-mitchell/recipes-phosphor/gpio/ |
| H A D | phosphor-gpio-monitor_%.bbappend | 4 file://phosphor-multi-gpio-monitor.json \ 5 file://phosphor-multi-gpio-presence.json \ 8 SYSTEMD_SERVICE:${PN}-monitor += " \ 9 ampere-host-shutdown-ack@.service \ 10 ampere-host-reboot@.service \ 13 FILES:${PN}-monitor += " \ 14 ${datadir}/${PN}/phosphor-multi-gpio-monitor.json \ 16 FILES:${PN}-presence += " \ 17 ${datadir}/${PN}/phosphor-multi-gpio-presence.json \ 21 install -d ${D}${bindir} [all …]
|
| /openbmc/openbmc/meta-google/recipes-google/bare-metal-gpio-monitor/ |
| H A D | bare-metal-gpio-monitor_git.bb | 1 SUMMARY = "Monitor host GPIO in bare metal mode" 2 DESCRIPTION = "Monitor host GPIO in bare metal mode" 3 GOOGLE_MISC_PROJ = "bare-metal-host-monitor" 5 require ../google-misc/google-misc.inc 12 phosphor-logging \ 13 abseil-cpp \ 17 bare-metal-active \ 24 # List of host instances 25 # Assume single host labeled as host "0". Override this variable, as needed. 29 install -d ${D}${systemd_system_unitdir} [all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/State/ |
| H A D | README.md | 1 # BMC, Host, and Chassis State Management 5 The goal of the phosphor-state-manager repository is to control and track the 8 Host and Chassis state interfaces. These interfaces will be the mechanism by 24 2. _Host_ : The host is either (Off), (Running), or it's (Quiesced). Running 26 request the host be in a (Off), (On), or (Reboot) state. More details on 27 different Reboot options below. Quiesced means the host OS is in a quiesce 32 power to the chassis. The Chassis being on is a pre-req to the Host being 50 `/xyz/openbmc_project/state/host<instance>` 63 will include BMC, host and chassis. This will support hard power cycle of 66 In multi-host or multi-chassis system, instance number can be used from 1-N, as [all …]
|
| /openbmc/phosphor-state-manager/service_files/ |
| H A D | phosphor-discover-system-state@.service | 2 Description=Reboot Host %i If Enabled 3 Wants=mapper-wait@-xyz-openbmc_project-control-host%i-power_restore_policy.service 4 After=mapper-wait@-xyz-openbmc_project-control-host%i-power_restore_policy.service 5 Wants=mapper-wait@-xyz-openbmc_project-state-host%i.service 6 After=mapper-wait@-xyz-openbmc_project-state-host%i.service 7 Wants=mapper-wait@-xyz-openbmc_project-state-chassis%i.service 8 After=mapper-wait@-xyz-openbmc_project-state-chassis%i.service 9 Wants=mapper-wait@-xyz-openbmc_project-state-bmc0.service 10 After=mapper-wait@-xyz-openbmc_project-state-bmc0.service 11 After=phosphor-reset-chassis-on@%i.service [all …]
|
| H A D | xyz.openbmc_project.State.ScheduledHostTransition@.service | 2 Description=Phosphor Scheduled Host%i Transition Manager 3 Wants=xyz.openbmc_project.State.Host@%i.service 4 After=xyz.openbmc_project.State.Host@%i.service 7 ExecStart=/usr/bin/phosphor-scheduled-host-transition --host %i 13 WantedBy=multi-user.target
|
| /openbmc/qemu/hw/pci-host/ |
| H A D | remote.c | 2 * Remote PCI host device 4 * Unlike PCI host devices that model physical hardware, the purpose 5 * of this PCI host is to host multi-process QEMU devices. 7 * Multi-process QEMU extends the PCI host of a QEMU machine into a 12 * This PCI host is purely a container for PCI devices. It's fake in the 13 * sense that the guest never sees this PCI host and has no way of 20 * See the COPYING file in the top-level directory. 29 #include "hw/qdev-properties.h" 30 #include "hw/pci-host/remote.h" 44 pci->bus = pci_root_bus_new(DEVICE(s), "remote-pci", in remote_pcihost_realize() [all …]
|
| /openbmc/openbmc/meta-facebook/meta-yosemite4/recipes-phosphor/images/ |
| H A D | fb-yosemite4-phosphor-image.inc | 2 # causing that multi-user.target never complete. 3 # If multi-user.target doesn't complete, 4 # the obmc-host-startmin@.target couldn't start. 5 # In that case, BMC couldn't set current host state to "Running". 7 # Temporarily add libusb1 to allow side-loading of a BIOS/BIC update 13 # Temporarily add plat-svc for gpio initialization 15 plat-svc \ 17 # Enable obmc-phosphor-buttons which needed by debug card function. 19 phosphor-gpio-monitor \ 20 obmc-phosphor-buttons-signals \ [all …]
|
| /openbmc/openbmc/meta-openpower/recipes-phosphor/host/ |
| H A D | op-proc-control-systemd-links.bb | 4 LICENSE = "Apache-2.0" 5 LIC_FILES_CHKSUM = "file://${COREBASE}/meta/files/common-licenses/Apache-2.0;md5=89aea4e17d99a7cacd… 9 RDEPENDS:${PN} += "op-proc-control" 10 RDEPENDS:${PN} += "phosphor-state-manager-obmc-targets" 15 mkdir -p $D$systemd_system_unitdir/obmc-host-stop@0.target.wants 16 mkdir -p $D$systemd_system_unitdir/obmc-host-force-warm-reboot@0.target.requires 17 mkdir -p $D$systemd_system_unitdir/obmc-host-startmin@0.target.requires 18 mkdir -p $D$systemd_system_unitdir/obmc-host-startmin@0.target.wants 19 mkdir -p $D$systemd_system_unitdir/obmc-host-diagnostic-mode@0.target.requires 20 mkdir -p $D$systemd_system_unitdir/obmc-chassis-poweron@0.target.requires [all …]
|
| /openbmc/phosphor-state-manager/target_files/ |
| H A D | obmc-host-startmin@.target | 2 Description=Start Host%i Minimum 3 After=multi-user.target 4 Conflicts=obmc-host-stop@%i.target 5 Wants=obmc-host-start-pre@%i.target 6 Wants=obmc-host-starting@%i.target 7 Wants=obmc-host-started@%i.target 8 OnFailure=obmc-host-quiesce@%i.target
|
| H A D | obmc-host-stopping@.target | 2 Description=Host%i (Stopping) 3 After=multi-user.target 4 Wants=obmc-host-stop-pre@%i.target 5 After=obmc-host-stop-pre@%i.target 6 Wants=obmc-host-stopped@%i.target 7 Before=obmc-host-stopped@%i.target 8 Conflicts=obmc-host-startmin@%i.target 9 Conflicts=obmc-host-starting@%i.target
|
| H A D | obmc-host-stop-pre@.target | 2 Description=Stop Host%i (Pre) 3 After=multi-user.target 4 Wants=obmc-host-stopping@%i.target 5 Before=obmc-host-stopping@%i.target 6 Conflicts=obmc-host-startmin@%i.target
|
| H A D | obmc-host-started@.target | 2 Description=Host%i (Started) 3 After=multi-user.target 4 Wants=obmc-host-starting@%i.target 5 After=obmc-host-starting@%i.target 6 Conflicts=obmc-host-stop@%i.target
|
| H A D | obmc-host-starting@.target | 2 Description=Host%i (Starting) 3 After=multi-user.target 4 Wants=obmc-host-start-pre@%i.target 5 After=obmc-host-start-pre@%i.target 6 Conflicts=obmc-host-stop@%i.target
|
| H A D | obmc-host-stop@.target | 2 Description=Stop Host%i 3 After=multi-user.target 4 After=obmc-chassis-poweroff@%i.target 5 Conflicts=obmc-host-startmin@%i.target 6 Wants=obmc-host-stop-pre@%i.target 7 Wants=obmc-host-stopping@%i.target 8 Wants=obmc-host-stopped@%i.target 9 OnFailure=obmc-chassis-poweroff@%i.target
|
| H A D | obmc-host-diagnostic-mode@.target | 2 # This target is activated when the host is 4 # debug a user or self detected error in the host 5 Description=Diagnostic Mode Collection for Host%i 6 After=multi-user.target 7 Conflicts=obmc-host-startmin@%i.target
|
| H A D | obmc-host-stopped@.target | 2 Description=Host%i (Stopped) 3 After=multi-user.target 4 Wants=obmc-host-stopping@%i.target 5 After=obmc-host-stopping@%i.target 6 Before=obmc-power-stop-pre@%i.target 7 Conflicts=obmc-host-startmin@%i.target
|
| H A D | obmc-host-start@.target | 2 Description=Start Host%i 3 After=multi-user.target 4 Conflicts=obmc-host-stop@%i.target 5 OnFailure=obmc-host-quiesce@%i.target
|
| /openbmc/openbmc/meta-hpe/meta-common/recipes-hpe/host/host-boot-enable/ |
| H A D | host-boot-enable.service | 2 Description=Enable Host Boot 3 Wants=phosphor-ipmi-host.service 4 After=phosphor-ipmi-host.service 8 ExecStart=/bin/sh -c "host-boot-enable.sh" 9 SyslogIdentifier=host-boot-enable 15 WantedBy=multi-user.target
|
| /openbmc/phosphor-buttons/src/ |
| H A D | button_handler.cpp | 7 #include <phosphor-logging/lg2.hpp> 10 #include <xyz/openbmc_project/State/Host/server.hpp> 27 {"chassis-on", Chassis::Transition::On}, 28 {"chassis-off", Chassis::Transition::Off}, 29 {"chassis-cycle", Chassis::Transition::PowerCycle}}; 32 constexpr auto hostIface = "xyz.openbmc_project.State.Host"; 54 /* So far, there are two modes for multi-host power control in Handler() 55 - host select button mode, e.g.: Yosemite V2 in Handler() 56 only one power button with host select switch, in Handler() 57 which's interface for handling target host, in Handler() [all …]
|