Home
last modified time | relevance | path

Searched full:pinhole (Results 1 – 11 of 11) sorted by relevance

/openbmc/phosphor-state-manager/
H A Dbmc_state_manager.cpp321 // reset-cause-pinhole gpio to see if it is the reason for the reboot in discoverLastRebootCause()
323 phosphor::state::manager::utils::getGpioValue("reset-cause-pinhole"); in discoverLastRebootCause()
325 // A 0 indicates a pinhole reset occurred in discoverLastRebootCause()
328 info("The BMC reset was caused by a pinhole reset"); in discoverLastRebootCause()
331 // Generate log telling user a pinhole reset has occurred in discoverLastRebootCause()
341 // Note that a pinhole reset will remove AC power to the chassis in discoverLastRebootCause()
342 // on some systems so we always want to look for the pinhole reset in discoverLastRebootCause()
H A Dmeson.options165 'run-apr-on-pinhole-reset',
168 description: 'run APR when BMC has been rebooted due to pinhole action',
H A Dchassis_state_manager.cpp135 // was not a pinhole reset, log an error in determineInitialState()
154 // 0 indicates pinhole reset. 1 is NOT pinhole reset in determineInitialState()
156 "reset-cause-pinhole") != 0) in determineInitialState()
169 info("Pinhole reset"); in determineInitialState()
H A Ddiscover_system_state.cpp82 // If the BMC was rebooted due to a user initiated pinhole reset, do not in main()
99 "BMC was reset due to pinhole reset, no power restore policy will be run"); in main()
H A Dmeson.build44 conf.set10('RUN_APR_ON_PINHOLE_RESET', get_option('run-apr-on-pinhole-reset'))
/openbmc/docs/designs/
H A Ddevice-tree-gpio-naming.md158 #### reset-cause-pinhole
160 The pinhole reset cause will be utilized by BMC firmware to know when it has
161 been reset due to a user initiated pinhole reset. This is commonly done in error
164 after the BMC reset to know the reason for the reboot was a pinhole reset.
H A Dpower-recovery.md105 pgood pin. Blackouts can be intentionally triggered by a user (i.e a pinhole
/openbmc/openbmc/meta-phosphor/recipes-phosphor/state/
H A Dphosphor-state-manager_git.bb58 # Allow run APR when BMC has been rebooted due to pinhole action
59 PACKAGECONFIG[run-apr-on-pinhole-reset] = "-Drun-apr-on-pinhole-reset=true,-Drun-apr-on-pinhole-res…
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/State/
H A DBMC.interface.yaml81 Last reboot is caused by pinhole reset
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/snort/snort/
H A Ddisable-run-test-program-while-cross-compiling.patch179 AC_MSG_CHECKING([for separate IP versions on pinhole endpoints])
/openbmc/phosphor-logging/extensions/openpower-pels/registry/
H A Dmessage_registry.json1183 "Description": "User initiated a pinhole reset via the op-panel",
1184 "Message": "User initiated a pinhole reset via the op-panel",
1187 "pinhole reset was performed on the BMC, resulting in a ",