Lines Matching full:platform

75 and the actual recovery steps taken are platform dependent.  The
114 The actual steps taken by a platform to recover from a PCI error
115 event will be platform-dependent, but will follow the general
127 Platform calls the error_detected() callback on every instance of
131 the platform (the slot will be isolated on powerpc). The driver may
158 then the platform should re-enable IOs on the slot (or do nothing in
159 particular, if the platform doesn't isolate slots), and recovery
165 If the platform is unable to recover the slot, the next step
189 The platform re-enables MMIO to the device (but typically not the
199 link reset was performed by the HW. If the platform can't just re-enable IOs
205    The following is proposed; no platform implements this yet:
235 If all drivers returned PCI_ERS_RESULT_RECOVERED, then the platform
238 If any driver returned PCI_ERS_RESULT_NEED_RESET, then the platform
243 The platform resets the link.  This is a PCI-Express specific step
251 the platform will perform a slot reset on the requesting PCI device(s).
252 The actual steps taken by a platform to perform a slot reset
253 will be platform-dependent. Upon completion of slot reset, the
254 platform will call the device slot_reset() callback.
274 If the platform supports PCI hotplug, then the reset might be
277 It is important for the platform to restore the PCI config space
292 callback, the platform will call resume() to complete the sequence,
296 it can't get the device operational after reset.  If the platform
299 be recovered, there is nothing more that can be done;  the platform
325 Platform proceeds either to STEP 5 (Resume Operations) or STEP 6 (Permanent
337 The platform will call the resume() callback on all affected device
344 At this point, if a new error happens, the platform will restart
349 A "permanent failure" has occurred, and the platform cannot recover
350 the device.  The platform will call error_detected() with a
359 The platform will typically notify the system operator of the
373 The way the callbacks are called is platform policy. A platform with
381 The current policy is to turn this into a platform policy.
393    return IRQ_NOTHANDLED. It's up to the platform to deal with that
395    the error handling. It is expected that the platform "knows" which
405    Implementation details for the powerpc platform are discussed in