Lines Matching full:an
5 A callout is typically an indication of a faulty hardware component in a system.
6 In OpenBMC, a callout is defined as any other error, via a YAML file. An example
7 would be `xyz.openbmc_project.Error.Callout.IIC`, to indicate an IIC callout.
10 is familiar to them, such as a sysfs entry, or an IIC address. It would be up to
16 An OpenBMC error has associated metadata, the same is true for a callout. Such
17 metadata would be defined in the callout YAML interface. Here is an example (for
29 An application wanting to add an IIC callout will have to provide values for the
31 figure out that this is in fact an IIC callout.
33 A callout is typically associated with an error log. For eg,
34 `xyz.openbmc_project.Error.Foo` may want to add an IIC callout. This is
45 include Callout.IIC's as well, so an application wanting to add an IIC callout
48 figure out that the error Foo includes an IIC callout.
63 This way, say an application wants to express an IIC callout in terms of a
67 this as an IIC callout.
74 Taking an example of a generic device callout here, but this would be the flow
77 - An application commits an error that has associated callout metadata. This
82 metadata to one or more inventory object paths, and will create an association
87 - Generated code : consider a case where an application wants to callout an
94 on an IIC bus, and make use of the code generated to map the device to