Home
last modified time | relevance | path

Searched refs:chassis (Results 1 – 25 of 600) sorted by relevance

12345678910>>...24

/openbmc/openbmc/meta-ibm/meta-genesis3/recipes-phosphor/gpio/phosphor-gpio-monitor/
H A Ddependencies.conf4 Wants=mapper-wait@-xyz-openbmc_project-inventory-system-chassis-motherboard-dimm_a0.service
5 Wants=mapper-wait@-xyz-openbmc_project-inventory-system-chassis-motherboard-dimm_a1.service
6 Wants=mapper-wait@-xyz-openbmc_project-inventory-system-chassis-motherboard-dimm_b0.service
7 Wants=mapper-wait@-xyz-openbmc_project-inventory-system-chassis-motherboard-dimm_b1.service
8 Wants=mapper-wait@-xyz-openbmc_project-inventory-system-chassis-motherboard-dimm_c0.service
9 Wants=mapper-wait@-xyz-openbmc_project-inventory-system-chassis-motherboard-dimm_c1.service
10 Wants=mapper-wait@-xyz-openbmc_project-inventory-system-chassis-motherboard-dimm_d0.service
11 Wants=mapper-wait@-xyz-openbmc_project-inventory-system-chassis-motherboard-dimm_d1.service
12 Wants=mapper-wait@-xyz-openbmc_project-inventory-system-chassis-motherboard-dimm_e0.service
13 Wants=mapper-wait@-xyz-openbmc_project-inventory-system-chassis-motherboard-dimm_e1.service
[all …]
/openbmc/openbmc/meta-ibm/meta-sbp1/recipes-phosphor/gpio/phosphor-gpio-monitor/
H A Ddependencies.conf4 Wants=mapper-wait@-xyz-openbmc_project-inventory-system-chassis-motherboard-dimm_c0a1.service
5 Wants=mapper-wait@-xyz-openbmc_project-inventory-system-chassis-motherboard-dimm_c0a2.service
6 Wants=mapper-wait@-xyz-openbmc_project-inventory-system-chassis-motherboard-dimm_c0b1.service
7 Wants=mapper-wait@-xyz-openbmc_project-inventory-system-chassis-motherboard-dimm_c0b2.service
8 Wants=mapper-wait@-xyz-openbmc_project-inventory-system-chassis-motherboard-dimm_c0c1.service
9 Wants=mapper-wait@-xyz-openbmc_project-inventory-system-chassis-motherboard-dimm_c0c2.service
10 Wants=mapper-wait@-xyz-openbmc_project-inventory-system-chassis-motherboard-dimm_c0d1.service
11 Wants=mapper-wait@-xyz-openbmc_project-inventory-system-chassis-motherboard-dimm_c0d2.service
12 Wants=mapper-wait@-xyz-openbmc_project-inventory-system-chassis-motherboard-dimm_c0e1.service
13 Wants=mapper-wait@-xyz-openbmc_project-inventory-system-chassis-motherboard-dimm_c0e2.service
[all …]
/openbmc/phosphor-power/phosphor-regulators/docs/
H A Dmultiple_chassis.md5 A BMC-based system can contain one or more chassis. A chassis is typically a
9 A chassis can be stand-alone, such as a tower or desktop. A chassis can also be
12 For the `phosphor-regulators` application, the term "single chassis system"
13 means the system type has a maximum configuration of one chassis. If the system
14 type has a maximum configuration of multiple chassis, then it is considered a
15 "multiple chassis system" even if the current system only contains one chassis.
18 does not support powering on/off individual chassis independent of the rest of
21 ## Defining the chassis in a system
24 more [chassis](config_file/chassis.md) objects. Each chassis object corresponds
25 to a physical chassis in the system.
[all …]
/openbmc/openbmc/meta-facebook/meta-ventura/recipes-phosphor/state/
H A Dphosphor-state-manager_%.bbappend5 obmc-chassis-powerreset@{}.target.requires/phosphor-reset-chassis-on@{}.service \
6 obmc-chassis-powerreset@{}.target.requires/phosphor-reset-chassis-running@{}.service \
7 obmc-chassis-poweroff@{}.target.requires/obmc-power-stop@{}.service \
8 obmc-chassis-poweron@{}.target.requires/obmc-power-start@{}.service \
13 RRECOMMENDS:${PN}-chassis:remove = " ${PN}-chassis-poweron-log"
15 SYSTEMD_SERVICE:${PN}-chassis:remove = "phosphor-reset-chassis-on@.service"
16 SYSTEMD_SERVICE:${PN}-chassis:remove = "phosphor-reset-chassis-running@.service"
17 SYSTEMD_SERVICE:${PN}-chassis:remove = "obmc-power-start@.service"
18 SYSTEMD_SERVICE:${PN}-chassis:remove = "obmc-power-stop@.service"
21 file://chassis-powercycle \
[all …]
/openbmc/openbmc/meta-facebook/meta-minerva/recipes-phosphor/state/
H A Dphosphor-state-manager_%.bbappend5 obmc-chassis-powerreset@{}.target.requires/phosphor-reset-chassis-on@{}.service \
6 obmc-chassis-powerreset@{}.target.requires/phosphor-reset-chassis-running@{}.service \
7 obmc-chassis-poweroff@{}.target.requires/obmc-power-stop@{}.service \
8 obmc-chassis-poweron@{}.target.requires/obmc-power-start@{}.service \
13 RRECOMMENDS:${PN}-chassis:remove = " ${PN}-chassis-poweron-log"
15 SYSTEMD_SERVICE:${PN}-chassis:remove = "phosphor-reset-chassis-on@.service"
16 SYSTEMD_SERVICE:${PN}-chassis:remove = "phosphor-reset-chassis-running@.service"
17 SYSTEMD_SERVICE:${PN}-chassis:remove = "obmc-power-start@.service"
18 SYSTEMD_SERVICE:${PN}-chassis:remove = "obmc-power-stop@.service"
21 file://chassis-powercycle \
[all …]
/openbmc/phosphor-power/phosphor-power-sequencer/docs/
H A Dmultiple_chassis.md5 A BMC-based system can contain one or more chassis. A chassis is typically a
9 A chassis can be stand-alone, such as a tower or desktop. A chassis can also be
12 For the `phosphor-power-sequencer` application, the term "single chassis system"
13 means the system type has a maximum configuration of one chassis. If the system
14 type has a maximum configuration of multiple chassis, then it is considered a
15 "multiple chassis system" even if the current system only contains one chassis.
17 ## Differences between single and multiple chassis systems
19 ### System and chassis power state
21 In a single chassis system, the system and chassis power state are identical.
24 In a multiple chassis system, each chassis has its own power state. Even if the
[all …]
H A Dmonitoring_chassis_pgood.md5 The power sequencer device provides a chassis power good (pgood) signal. This
9 chassis pgood signal from a named GPIO. For more information, see
12 The resulting chassis pgood value is used to set the `pgood` property for the
13 chassis. See [Chassis Status](chassis_status.md) for more information on this
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
27 - The `Available` property of the chassis changes to false.
31 If `phosphor-power-sequencer` is unable to read the chassis power good signal
34 - If this is a single chassis system:
[all …]
H A Dchassis_status.md5 There are multiple D-Bus interfaces and properties that describe the chassis
16 the chassis. 0 means off, and 1 means on. This property is set when the system
20 of the chassis. 0 means off, and 1 means on. This is the actual, current power
21 state. This property is set based on the chassis power good signal from the
28 - `/org/openbmc/control/power1`: Represents chassis 1
29 - `/org/openbmc/control/power2`: Represents chassis 2
31 - `/org/openbmc/control/powerN`: Represents chassis N
33 ### Single chassis system
35 On a single chassis system, only the first two object paths are published,
36 representing the entire system and chassis 1. The values of the `state` and
[all …]
H A Dpowering_on.md14 system. In a multiple chassis system, `phosphor-power-sequencer` does not
15 support powering on individual chassis independent of the rest of the system.
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
31 that is being powered on. It will set `state` to 0 for each chassis not being
34 If no chassis are in the proper status to power on, `phosphor-power-sequencer`
[all …]
H A Dpower_loss.md18 In a multiple chassis system, a brownout or blackout might only occur in some of
19 the chassis.
23 If the chassis was powered off when the brownout occurred, the
26 If the chassis was powered on when the brownout occurred, the power sequencer
27 device will normally change the chassis power good (pgood) signal from true to
35 ### Single chassis system
41 automatically powered on again by the `phosphor-chassis-state-manager`
44 ### Multiple chassis system
46 If the blackout affects all chassis, the system loses all power. It will behave
47 as described above for a single chassis system.
[all …]
/openbmc/openbmc/meta-facebook/meta-yosemite5/recipes-phosphor/state/
H A Dphosphor-state-manager_%.bbappend5 # NOTE: The YV5 SCM shares the blade/chassis standby power rail.
6 # As a result, the chassis is always powered on and does not support
7 # independent chassis power on/off control; only chassis power cycle
12 obmc-chassis-poweron@{}.target.wants/chassis-poweron@{}.service \
13 obmc-chassis-poweron@{}.target.wants/phosphor-reset-host-recovery@{}.service \
14 obmc-chassis-poweron@{}.target.requires/obmc-power-start@{}.service \
15 obmc-chassis-poweron@{}.target.requires/phosphor-set-chassis
[all...]
/openbmc/phosphor-power/phosphor-power-sequencer/test/
H A Dchassis_tests.cpp17 #include "chassis.hpp"
55 std::string powerControlGPIOName{"power-chassis-control"}; in TEST()
56 std::string powerGoodGPIOName{"power-chassis-good"}; in TEST()
71 * @param chassis Chassis object in TEST()
74 MockChassisStatusMonitor& getMockStatusMonitor(Chassis& chassis) in TEST()
76 return static_cast<MockChassisStatusMonitor&>(chassis.getStatusMonitor()); in TEST()
82 std::string inventoryPath{"/xyz/openbmc_project/inventory/system/chassis"}; in TEST()
93 Chassis chassis{number, inventoryPath, std::move(powerSequencers), in TEST()
96 EXPECT_EQ(chassis.getNumber(), number); in TEST()
97 EXPECT_EQ(chassis in TEST()
61 Chassis chassis{number, inventoryPath, std::move(powerSequencers)}; TEST() local
75 Chassis chassis{number, inventoryPath, std::move(powerSequencers)}; TEST() local
86 Chassis chassis{number, inventoryPath, std::move(powerSequencers)}; TEST() local
99 Chassis chassis{number, inventoryPath, std::move(powerSequencers)}; TEST() local
[all...]
H A Dconfig_file_parser_tests.cpp16 #include "chassis.hpp"
255 "chassis": [ in TEST()
274 auto chassis = parse(pathName); in TEST()
276 EXPECT_EQ(chassis.size(), 2); in TEST()
277 EXPECT_EQ(chassis[0]->getNumber(), 1); in TEST()
278 EXPECT_EQ(chassis[0]->getInventoryPath(), in TEST()
280 EXPECT_EQ(chassis[1]->getNumber(), 2); in TEST()
281 EXPECT_EQ(chassis[1]->getInventoryPath(), in TEST()
295 "chassis": [ in TEST()
343 "inventory_path": "/xyz/openbmc_project/inventory/system/chassis in TEST()
273 auto chassis = parse(pathName); TEST() local
374 auto chassis = parseChassis(element, chassisTemplates); TEST() local
396 auto chassis = parseChassis(element, chassisTemplates); TEST() local
419 auto chassis = parseChassis(element, chassisTemplates); TEST() local
596 auto chassis = parseChassisArray(element, chassisTemplates); TEST() local
616 auto chassis = parseChassisArray(element, chassisTemplates); TEST() local
640 auto chassis = parseChassisArray(element, chassisTemplates); TEST() local
729 auto chassis = TEST() local
771 auto chassis = TEST() local
2507 auto chassis = parseRoot(element); TEST() local
2548 auto chassis = parseRoot(element); TEST() local
[all...]
/openbmc/openbmc/meta-facebook/meta-fbdarwin/recipes-phosphor/state/
H A Dphosphor-state-manager_%.bbappend7 file://chassis-powercycle \
8 file://chassis-powercycle@.service \
16 obmc-chassis-powerreset@{}.target.requires/phosphor-reset-chassis-on@{}.service \
17 obmc-chassis-powerreset@{}.target.requires/phosphor-reset-chassis-running@{}.service \
18 obmc-chassis-poweroff@{}.target.requires/obmc-power-stop@{}.service \
19 obmc-chassis-poweron@{}.target.requires/obmc-power-start@{}.service \
22 SYSTEMD_SERVICE:${PN}-chassis:remove = "phosphor-reset-chassis-on@.service"
23 SYSTEMD_SERVICE:${PN}-chassis:remove = "phosphor-reset-chassis-running@.service"
24 SYSTEMD_SERVICE:${PN}-chassis:remove = "obmc-power-start@.service"
25 SYSTEMD_SERVICE:${PN}-chassis:remove = "obmc-power-stop@.service"
[all …]
/openbmc/openbmc/meta-facebook/meta-yosemite4/recipes-phosphor/state/
H A Dphosphor-state-manager_%.bbappend19 obmc-chassis-powerreset@{}.target.requires/phosphor-reset-chassis-on@{}.service \
20 obmc-chassis-powerreset@{}.target.requires/phosphor-reset-chassis-running@{}.service \
21 obmc-chassis-poweroff@{}.target.requires/obmc-power-stop@{}.service \
22 obmc-chassis-poweron@{}.target.requires/obmc-power-start@{}.service \
25 SYSTEMD_SERVICE:${PN}-chassis:remove = "phosphor-reset-chassis-on@.service"
26 SYSTEMD_SERVICE:${PN}-chassis:remove = "phosphor-reset-chassis-running@.service"
27 SYSTEMD_SERVICE:${PN}-chassis:remove = "obmc-power-start@.service"
28 SYSTEMD_SERVICE:${PN}-chassis:remove = "obmc-power-stop@.service"
30 # When we power off the host, we do not want to do a full chassis power-off
34 obmc-host-shutdown@{}.target.requires/obmc-chassis-poweroff@{}.target \
[all …]
/openbmc/openbmc/meta-facebook/meta-harma/recipes-phosphor/state/
H A Dphosphor-state-manager_%.bbappend10 obmc-chassis-powerreset@{}.target.requires/phosphor-reset-chassis-on@{}.service \
11 obmc-chassis-powerreset@{}.target.requires/phosphor-reset-chassis-running@{}.service \
12 obmc-chassis-poweroff@{}.target.requires/obmc-power-stop@{}.service \
13 obmc-chassis-poweron@{}.target.requires/obmc-power-start@{}.service \
18 obmc-chassis-poweron@{}.target.wants/chassis-poweron@{}.service \
19 obmc-chassis-hard-poweroff@{}.target.wants/chassis-poweroff@{}.service \
20 obmc-chassis-powercycle@{}.target.wants/chassis-powercycle@{}.service \
25 obmc-chassis-poweron@{}.target.requires/chassis-poweron@{}.service \
26 obmc-chassis-powercycle@{}.target.requires/chassis-powercycle@{}.service \
63 #We need to ensure that the chassis power is always on.
[all …]
/openbmc/openbmc/meta-facebook/meta-santabarbara/recipes-phosphor/state/
H A Dphosphor-state-manager_%.bbappend10 obmc-chassis-powerreset@{}.target.requires/phosphor-reset-chassis-on@{}.service \
11 obmc-chassis-powerreset@{}.target.requires/phosphor-reset-chassis-running@{}.service \
12 obmc-chassis-poweroff@{}.target.requires/obmc-power-stop@{}.service \
13 obmc-chassis-poweron@{}.target.requires/obmc-power-start@{}.service \
18 obmc-chassis-poweron@{}.target.wants/chassis-poweron@{}.service \
19 obmc-chassis-hard-poweroff@{}.target.wants/chassis-poweroff@{}.service \
20 obmc-chassis-powercycle@{}.target.wants/chassis-powercycle@{}.service \
25 obmc-chassis-poweron@{}.target.requires/chassis-poweron@{}.service \
26 obmc-chassis-powercycle@{}.target.requires/chassis-powercycle@{}.service \
63 #We need to ensure that the chassis power is always on.
[all …]
/openbmc/phosphor-power/phosphor-power-sequencer/docs/config_file/
H A Dchassis.md1 # chassis chapter
5 A chassis within the system.
8 as CPUs, fans, power supplies, and PCIe cards. A chassis can be stand-alone,
9 such as a tower or desktop. A chassis can also be designed to be mounted in an
12 A chassis only needs to be defined in the config file if it contains a power
17 In a multiple chassis system, two or more of the chassis may have the same
20 A [chassis template](chassis_template.md) can be used to avoid duplicate data.
23 chassis template.
29 | comments | no | array of strings | One or more comment lines describing this chassis
[all...]
H A Dchassis_template.md7 In a multiple chassis system, two or more of the [chassis](chassis.md) may have
8 the same hardware design. The corresponding chassis objects in the config file
11 A chassis template defines the power sequencers, GPIOs, and voltage rails in a
12 chassis. One or more property values in the template contain variables, such as
13 `${chassis_number}`, to support chassis-specific values.
15 Multiple chassis can use the template rather than duplicating the information.
16 The individual chassis specify values for the template variables, such as
21 Variables are specified in property values of a chassis templat
[all...]
H A Dconfig_file.md12 …(chassis_template.md) | One or more chassis templates. Templates are used to avoid duplicate data …
13 | chassis | yes | array of [chassis](chassis.md) | One or more ch…
19 "comments": [ "Config file for a FooBar one-chassis system" ],
20 "chassis": [
23 "inventory_path": "/xyz/openbmc_project/inventory/system/chassis",
38 "inventory_path": "/xyz/openbmc_project/inventory/system/chassis${chassis_number}",
44 "chassis": [
/openbmc/openbmc/meta-facebook/meta-bletchley/recipes-phosphor/state/
H A Dphosphor-state-manager_%.bbappend4 file://chassis-powercycle \
5 file://chassis-powercycle@.service \
6 file://chassis-poweroff@.service \
7 file://chassis-poweron \
8 file://chassis-poweron@.service \
21 install -m 0755 ${UNPACKDIR}/chassis-powercycle ${D}${libexecdir}/${PN}/
22 install -m 0755 ${UNPACKDIR}/chassis-poweron ${D}${libexecdir}/${PN}/
43 obmc-chassis-powerreset@{}.target.requires/phosphor-reset-chassis-on@{}.service \
44 obmc-chassis-powerreset@{}.target.requires/phosphor-reset-chassis-running@{}.service \
45 obmc-chassis-poweroff@{}.target.requires/obmc-power-stop@{}.service \
[all …]
/openbmc/openbmc/meta-facebook/meta-anacapa/recipes-phosphor/state/
H A Dphosphor-state-manager_%.bbappend10 obmc-chassis-powerreset@{}.target.requires/phosphor-reset-chassis-on@{}.service \
11 obmc-chassis-powerreset@{}.target.requires/phosphor-reset-chassis-running@{}.service \
12 obmc-chassis-poweroff@{}.target.requires/obmc-power-stop@{}.service \
13 obmc-chassis-poweron@{}.target.requires/obmc-power-start@{}.service \
18 obmc-chassis-poweron@{}.target.wants/chassis-poweron@{}.service \
19 obmc-chassis-powercycle@{}.target.wants/chassis-powercycle@{}.service \
24 obmc-chassis-poweron@{}.target.requires/chassis-poweron@{}.service \
25 obmc-chassis-powercycle@{}.target.requires/chassis-powercycle@{}.service \
62 #We need to ensure that the chassis power is always on.
64 obmc-host-shutdown@{}.target.requires/obmc-chassis-poweroff@{}.target \
[all …]
/openbmc/openbmc/meta-facebook/meta-catalina/recipes-phosphor/state/
H A Dphosphor-state-manager_%.bbappend52 # Add services for the chassis power operations.
54 obmc-chassis-poweron@{}.target.requires/chassis-poweron@{}.service \
55 obmc-chassis-powercycle@{}.target.requires/chassis-powercycle@{}.service \
59 # `org.openbmc` interface but instead install our own chassis-poweron and
60 # chassis-poweroff.
62 obmc-chassis-poweron@{}.target.requires/obmc-power-start@{}.service \
63 obmc-chassis-poweroff@{}.target.requires/obmc-power-stop@{}.service \
66 # The obmc-chassis-powerreset target is used to determine the state of the host
71 obmc-chassis-powerreset@{}.target.requires/phosphor-reset-chassis-on@{}.service \
72 obmc-chassis-powerreset@{}.target.requires/phosphor-reset-chassis-running@{}.service \
[all …]
/openbmc/phosphor-power/phosphor-power-supply/docs/
H A DMultiChassis.md5 Currently, **phosphor-psu-monitor** operates on a **single chassis**.
14 /xyz/openbmc_project/inventory/system/chassis/motherboard/powersupply0
20 To support **multi-chassis**, the **phosphor-psu-monitor** requires the
25 physical chassis.
26 - Find all PSUs associated with each chassis.
37 - Chassis class constructor take parameters D-Bus connection object, chassis
41 - Function to get chassis status
45 - Add method to retrieve a list of chassis objects from the **inventory
46 manager** and store them in a vector of chassis. Each chassis object listens
47 for D-BUS events to track chassis PGOOD Status.
[all …]
/openbmc/phosphor-power/phosphor-regulators/src/
H A Ddevice.cpp88 void Device::configure(Services& services, System& system, Chassis& chassis) in configure() argument
91 if (isPresent(services, system, chassis)) in configure()
96 configuration->execute(services, system, chassis, *this); in configure()
102 rail->configure(services, system, chassis, *this); in configure()
108 Chassis& chassis) in detectPhaseFaults() argument
111 if (isPresent(services, system, chassis)) in detectPhaseFaults()
116 phaseFaultDetection->execute(services, system, chassis, *this); in detectPhaseFaults()
122 Chassis& chassis) in monitorSensors() argument
125 if (isPresent(services, system, chassis)) in monitorSensors()
130 rail->monitorSensors(services, system, chassis, *this); in monitorSensors()

12345678910>>...24