Lines Matching refs:platform

73 and the actual recovery steps taken are platform dependent.  The
111 The actual steps taken by a platform to recover from a PCI error
112 event will be platform-dependent, but will follow the general
128 the platform (the slot will be isolated on powerpc). The driver may
154 then the platform should re-enable IOs on the slot (or do nothing in
155 particular, if the platform doesn't isolate slots), and recovery
161 If the platform is unable to recover the slot, the next step
183 The platform re-enables MMIO to the device (but typically not the
193 link reset was performed by the HW. If the platform can't just re-enable IOs
197 >>> The following is proposed; no platform implements this yet:
227 If all drivers returned PCI_ERS_RESULT_RECOVERED, then the platform
230 If any driver returned PCI_ERS_RESULT_NEED_RESET, then the platform
235 The platform resets the link, and then calls the link_reset() callback
244 check its recoverability status. If all is right, then the platform
250 The platform then proceeds to either STEP 4 (Slot Reset) or STEP 5
259 the platform will perform a slot reset on the requesting PCI device(s). 
260 The actual steps taken by a platform to perform a slot reset
261 will be platform-dependent. Upon completion of slot reset, the
262 platform will call the device slot_reset() callback.
282 If the platform supports PCI hotplug, then the reset might be
285 It is important for the platform to restore the PCI config space
300 callback, the platform will call resume() to complete the sequence,
304 it can't get the device operational after reset.  If the platform
307 be recovered, there is nothing more that can be done;  the platform
343 The platform will call the resume() callback on all affected device
350 At this point, if a new error happens, the platform will restart
355 A "permanent failure" has occurred, and the platform cannot recover
356 the device.  The platform will call error_detected() with a
365 The platform will typically notify the system operator of the
379 The way the callbacks are called is platform policy. A platform with
387 The current policy is to turn this into a platform policy.
399 return IRQ_NOTHANDLED. It's up to the platform to deal with that
401 the error handling. It is expected that the platform "knows" which
409 >>> Implementation details for the powerpc platform are discussed in