Home
last modified time | relevance | path

Searched refs:CALLOUT (Results 1 – 5 of 5) sorted by relevance

/openbmc/ibm-logging/
H A Dinterfaces.hpp27 CALLOUT, enumerator
H A Dmanager.cpp250 addChildInterface(objectPath, InterfaceType::CALLOUT, anyObject); in createCalloutObjects()
292 addChildInterface(objectPath, InterfaceType::CALLOUT, anyObject); in restoreCalloutObjects()
/openbmc/phosphor-logging/extensions/openpower-pels/
H A DREADME.md307 ### Using the message registry along with CALLOUT\_ entries
310 also contains one of aforementioned CALLOUT keys in the AdditionalData property,
311 then the PEL code will first add the callouts stemming from the CALLOUT items,
/openbmc/docs/development/
H A Dadd-new-system.md508 with a CALLOUT path. [phosphor-fru-fault-monitor][29] monitors the logs:
509 - Assert the related fault LED group when a log with the CALLOUT path is
/openbmc/phosphor-logging/
H A DREADME.md484 looking at new phosphor-logging entries being created, and if a CALLOUT\* is