/openbmc/openbmc/meta-facebook/meta-ventura/recipes-phosphor/gpio/phosphor-gpio-monitor/ |
H A D | ventura-phosphor-multi-gpio-monitor.json | 8 "power-good-assert@compute-tray-1.service", 12 "power-good-deassert@compute-tray-1.service", 24 "power-good-assert@compute-tray-2.service", 28 "power-good-deassert@compute-tray-2.service", 40 "power-good-assert@compute-tray-3.service", 44 "power-good-deassert@compute-tray-3.service", 56 "power-good-assert@compute-tray-4.service", 60 "power-good-deassert@compute-tray-4.service", 72 "power-good-assert@compute-tray-5.service", 76 "power-good-deassert@compute-tray-5.service", [all …]
|
H A D | power-good-deassert@.service | 2 Description=%i Power Good Status Deassert 6 ExecStart=/usr/libexec/phosphor-gpio-monitor/logging "%i power good deassert" "BLADE" "%i" 7 SyslogIdentifier=%i-power-good-deassert
|
H A D | power-good-assert@.service | 2 Description=%i Power Good Status Assert 6 ExecStart=/usr/libexec/phosphor-gpio-monitor/logging "%i power good assert" "BLADE" "%i" 7 SyslogIdentifier=%i-power-good-assert
|
H A D | led-blue-deassert@.service | 2 Description=%i Power Good LED Deassert 6 ExecStart=/usr/libexec/phosphor-gpio-monitor/frontled "%i" "power good LED" "deassert" 7 SyslogIdentifier=%i-power-good-led-deassert
|
H A D | led-blue-assert@.service | 2 Description=%i Power Good LED Assert 6 ExecStart=/usr/libexec/phosphor-gpio-monitor/frontled "%i" "power good LED" "assert" 7 SyslogIdentifier=%i-power-good-led-assert
|
/openbmc/phosphor-power/phosphor-power-sequencer/docs/ |
H A D | monitoring_chassis_pgood.md | 1 # Monitoring Chassis Power Good 5 The power sequencer device provides a chassis power good (pgood) signal. This 16 If the chassis pgood state is false when it should be true, a chassis power good 17 (pgood) fault has occurred. See [Power Good Faults](pgood_faults.md) for more 20 ## Unable to read chassis power good signal 22 `phosphor-power-sequencer` may become unable to read the chassis power good 31 If `phosphor-power-sequencer` is unable to read the chassis power good signal 36 read the chassis power good status. 44 read the chassis power good status. 56 If `phosphor-power-sequencer` is unable to read the chassis power good signal [all …]
|
H A D | powering_on.md | 28 - `Status` property is `Good` (if interface exists) 53 sequencer device will set the chassis power good (pgood) signal to true. 57 [Monitoring Chassis Power Good](monitoring_chassis_pgood.md). 59 When the chassis power good signal changes to true, `phosphor-power-sequencer` 75 ### Power good fault 83 [Power Good Faults](pgood_faults.md) for information on how the error is 86 ### Unable to read chassis power good signal 88 `phosphor-power-sequencer` may become unable to read the chassis power good 94 See [Monitoring Chassis Power Good](monitoring_chassis_pgood.md) for more
|
H A D | chassis_status.md | 19 `pgood` has a value of 0 or 1. `pgood` represents the power good (pgood) state 21 state. This property is set based on the chassis power good signal from the 69 If a power good fault occurs in a chassis after the system powered on, the 72 Eventually the system will be powered off due to the power good fault. See 73 [Power Good Faults](pgood_faults.md) for more information. 88 The chassis power good signal is read from the power sequencer device. Both the 89 `state` and `pgood` properties are set to the value of the power good signal. 90 For example, if the chassis power good is true, both `state` and `pgood` are set 95 good signal. For example, the chassis might not be present or might have no 112 - The chassis power good signal from the power sequencer will **not** be read. [all …]
|
H A D | named_gpios.md | 17 ## Chassis power good (pgood) 19 The power sequencer device provides a chassis power good (pgood) signal, 22 The `phosphor-power-sequencer` application reads the chassis power good signal 26 the standard GPIO name is `power-chassis-good`. See
|
H A D | multiple_chassis.md | 30 ### Chassis power good faults 32 If a single chassis system experiences a power good (pgood) fault, the system is 35 If a multiple chassis system experiences a power good (pgood) fault in one 39 See [Power Good Faults](pgood_faults.md) for more information.
|
/openbmc/qemu/tests/qapi-schema/ |
H A D | meson.build | 76 'doc-good.json', 227 output: ['doc-good-qapi-commands.c', 'doc-good-qapi-commands.h', 228 'doc-good-qapi-emit-events.c', 'doc-good-qapi-emit-events.h', 229 'doc-good-qapi-events.c', 'doc-good-qapi-events.h', 230 'doc-good-qapi-init-commands.c', 'doc-good-qapi-init-commands.h', 231 'doc-good-qapi-introspect.c', 'doc-good-qapi-introspect.h', 232 'doc-good-qapi-types.c', 'doc-good-qapi-types.h', 233 'doc-good-qapi-visit.c', 'doc-good-qapi-visit.h' ], 234 input: files('doc-good.json'), 236 '-p', 'doc-good-', '@INPUT0@' ], [all …]
|
/openbmc/openbmc/poky/meta/recipes-multimedia/gstreamer/ |
H A D | gstreamer1.0-meta-base.bb | 12 DEPENDS = "gstreamer1.0 gstreamer1.0-plugins-base gstreamer1.0-plugins-good ${DEPENDS_UGLY} ${DEPEN… 38 gstreamer1.0-plugins-good-autodetect \ 39 gstreamer1.0-plugins-good-soup" 49 gstreamer1.0-plugins-good-wavparse \ 50 gstreamer1.0-plugins-good-flac \ 55 gstreamer1.0-plugins-good-debug \ 61 gstreamer1.0-plugins-good-avi \ 62 gstreamer1.0-plugins-good-matroska \
|
/openbmc/openbmc/meta-facebook/meta-santabarbara/recipes-phosphor/gpio/ |
H A D | phosphor-gpio-monitor_%.bbappend | 6 assert-power-good-drop.service \ 9 deassert-power-good-drop.service \ 25 file://assert-power-good-drop \ 28 file://deassert-power-good-drop \ 56 install -m 0755 ${UNPACKDIR}/assert-power-good-drop ${D}${libexecdir}/${PN}/ 59 install -m 0755 ${UNPACKDIR}/deassert-power-good-drop ${D}${libexecdir}/${PN}/
|
/openbmc/openbmc/meta-facebook/meta-harma/recipes-phosphor/gpio/phosphor-gpio-monitor/ |
H A D | assert-power-good.service | 2 Description=Assert Power Good Status 6 ExecStart=/usr/libexec/phosphor-gpio-monitor/assert-power-good 8 SyslogIdentifier=assert-power-good
|
H A D | deassert-power-good.service | 2 Description=Deassert Power Good Status 6 ExecStart=/usr/libexec/phosphor-gpio-monitor/deassert-power-good 8 SyslogIdentifier=deassert-power-good
|
H A D | plat-phosphor-multi-gpio-monitor.json | 14 "Name": "power-hsc-good", 82 "power-rail-deassert-log@2_power-hsc-good.service", 87 "power-rail-assert-log@2_power-hsc-good.service", 94 "Name": "power-host-good", 100 "deassert-power-good.service", 102 "power-rail-deassert-log@2_power-host-good.service" 105 "assert-power-good.service", 106 "power-rail-assert-log@2_power-host-good.service" 123 "Name": "power-asic-good",
|
/openbmc/openbmc/meta-facebook/meta-santabarbara/recipes-phosphor/gpio/phosphor-gpio-monitor/ |
H A D | assert-power-good-drop.service | 2 Description=Assert Power Good Drop 6 ExecStart=/usr/libexec/phosphor-gpio-monitor/assert-power-good-drop 8 SyslogIdentifier=assert-power-good-drop
|
H A D | deassert-power-good-drop.service | 2 Description=Deassert Power Good Drop 6 ExecStart=/usr/libexec/phosphor-gpio-monitor/deassert-power-good-drop 8 SyslogIdentifier=deassert-power-good-drop
|
/openbmc/phosphor-power/phosphor-power-sequencer/src/ |
H A D | power_interface.hpp | 36 * Emit the power good signal 52 * Returns the power good of the chassis 53 * @return power good 58 * Returns the power good timeout 59 * @return power good timeout 70 * Sets the power good timeout 71 * @param timeout power good timeout
|
/openbmc/phosphor-state-manager/ |
H A D | chassis_check_power_status.cpp | 55 // If the chassis power status is not good, log an error and exit with in main() 60 "xyz.openbmc_project.State.Chassis.PowerStatus.Good") in main() 62 error("Chassis power status is not good: {CURRENT_PWR_STATUS}", in main() 74 // all good in main() 75 info("Chassis power status good, start power on"); in main()
|
/openbmc/openpower-hw-diags/util/ |
H A D | bin_stream.hpp | 41 /** @return True, if the state of the stream is good. */ 42 bool good() in good() function in util::BinFileReader 44 return iv_stream.good(); in good() 52 * @note After calling, check good() to determine if the operation was 138 /** @return True, if the state of the stream is good. */ 139 bool good() in good() function in util::BinFileWriter 141 return iv_stream.good(); in good() 149 * @note After calling, check good() to determine if the operation was
|
/openbmc/openbmc/poky/meta/files/common-licenses/ |
H A D | GLWTPL | 1 GLWT(Good Luck With That) Public License 13 GOOD LUCK WITH THAT PUBLIC LICENSE 25 Good luck and Godspeed.
|
/openbmc/openpower-hw-diags/test/ |
H A D | test-bin-stream.cpp | 46 ASSERT_TRUE(w.good()); in TEST() 49 ASSERT_TRUE(w.good()); in TEST() 60 ASSERT_TRUE(r.good()); in TEST() 63 ASSERT_TRUE(r.good()); in TEST()
|
/openbmc/openbmc/meta-facebook/meta-harma/recipes-phosphor/gpio/ |
H A D | phosphor-gpio-monitor_%.bbappend | 7 file://assert-power-good \ 8 file://assert-power-good.service \ 18 file://deassert-power-good \ 19 file://deassert-power-good.service \ 62 assert-power-good.service \ 65 deassert-power-good.service \ 113 install -m 0755 ${UNPACKDIR}/assert-power-good ${D}${libexecdir}/${PN}/ 114 install -m 0755 ${UNPACKDIR}/deassert-power-good ${D}${libexecdir}/${PN}/
|
/openbmc/u-boot/drivers/mtd/onenand/ |
H A D | onenand_bbt.c | 33 * tables and good / bad block identifiers. Same as check_pattern, but 55 * @param bd descriptor for the good/bad block search pattern 60 * for the given good/bad block identify pattern 133 * @param bd descriptor for the good/bad block search pattern 136 * for manufacturer / software marked good / bad blocks 181 * @param bd descriptor for the good/bad block search pattern 185 * marked good / bad blocks and writes the bad block table(s) to 227 * Define some generic bad / good block scan pattern which are used 228 * while scanning a device for factory marked good / bad blocks.
|