Lines Matching refs:callouts

12 - [Callouts](#callouts)
109 [here for details](#passing-callouts-in-with-the-additionaldata-property)
122 See [here for details](#passing-callouts-in-with-the-additionaldata-property)
126 This is used to pass in a device path to create callouts from. See
127 [here for details](#passing-callouts-in-with-the-additionaldata-property)
131 This is used to pass in an I2C bus and address to create callouts from. See
132 [here for details](#passing-callouts-in-with-the-additionaldata-property)
235 There are a few different ways to add callouts to a PEL. In all cases, the
236 callouts will be sorted from highest to lowest priority within the PEL after
239 ### Passing callouts in with the AdditionalData property
241 The PEL code can add callouts based on the values of special entries in the
281   will use data tables generated by the MRW to create the callouts.
293 ### Defining callouts in the message registry
296 message registry. This method allows the callouts to vary based on the system
312 then the PEL code will first add the callouts stemming from the CALLOUT items,
313 followed by the callouts from the message registry.
315 ### Specifying multiple callouts using JSON format FFDC files
317 Multiple callouts can be passed in by the creator at the time of PEL creation.
322 To specify that an FFDC file contains callouts, the format value for that FFDC
338 The JSON contains an array of callouts that must be in order of highest priority
339 to lowest, with a maximum of 10. Any callouts after the 10th will just be thrown
374 Normal hardware callouts must contain either the location code or inventory
400 added to callouts to specify failing devices on a FRU. These may be used during
427 The LocationCode field is not used with procedure callouts. Only the first 7
671 infrastructure during hardware procedure execution failures, also add callouts,