Lines Matching refs:that

21 offered, so that the affected PCI device(s) are reset and put back
29 a PCI hardware error has resulted in a bus disconnect, that event
38 is forced by the need to handle multi-function devices, that is,
39 devices that have multiple device drivers associated with them.
44 If any driver requests a slot reset, that is what will be done.
47 again notified, so that they may then perform any device setup/config
48 that may be required.  After these have all completed, a final
72 pci_driver. A driver that fails to provide the structure is "non-aware",
106 is assumed that the driver is not doing any direct recovery and requires
118 is isolated, in that all I/O is blocked: all reads return 0xffffffff,
130 is the proper "synchronization point", that is, it gives the driver
164 >>> The current powerpc implementation assumes that a device driver will
177 >>> assumes that the device driver has gone into an infinite loop
192 all drivers on a segment agree that they can try to recover and if no automatic
203 >>> segment, and thus invalidate the recovery that other devices
205 >>> into one of the next states, that is, link reset or slot reset.
212 		  guarantee that the driver will actually be
215 		  slot reset on platforms that support it.
237 and is done whenever a non-fatal error has been detected that can be
269 that is equivalent to what it would be after a fresh system
293 that the card is in a fresh state and is fully functional. The slot
307 be recovered, there is nothing more that can be done;  the platform
323 Drivers for PCI Express cards that require a fundamental reset must
347 that everything is back and running. This callback does not return
380 no slot reset capability may want to just "ignore" drivers that can't
382 recover. Keep in mind that in most real life cases, though, there will
388 That is, the recovery API only requires that:
390  - There is no guarantee that interrupt delivery can proceed from any
395  - There is no guarantee that interrupt delivery is stopped, that is,
396 a driver that gets an interrupt after detecting an error, or that detects
397 an error within the interrupt handler such that it prevents proper
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
403 with temporarily disabling that IRQ number during error processing (this