Lines Matching +full:re +full:- +full:initialization
1 .. SPDX-License-Identifier: GPL-2.0
8 :Authors: - Linas Vepstas <linasvepstas@gmail.com>
9 - Richard Lary <rlary@us.ibm.com>
10 - Mike Mason <mmlnx@us.ibm.com>
16 chipsets are able to deal with these errors; these include PCI-E chipsets,
17 and the PCI-host bridges found on IBM Power4, Power5 and Power6-based
32 including multiple instances of a device driver on multi-function
34 waiting for some i/o-space register to change, when it never will.
39 is forced by the need to handle multi-function devices, that is,
42 of reset it desires, the choices being a simple re-enabling of I/O
47 After a reset and/or a re-enabling of I/O, all drivers are
52 The biggest reason for choosing a kernel-based implementation rather
53 than a user-space implementation was the need to deal with bus
56 file system is disconnected, a user-space mechanism would have to go
62 for example, the SCSI-generic layer already provides significant
74 pci_driver. A driver that fails to provide the structure is "non-aware",
116 event will be platform-dependent, but will follow the general
120 -------------------
127 --------------------
144 - PCI_ERS_RESULT_CAN_RECOVER
149 - PCI_ERS_RESULT_NEED_RESET
152 - PCI_ERS_RESULT_DISCONNECT
159 then the platform should re-enable IOs on the slot (or do nothing in
175 Doing better requires complex multi-threaded logic in the error
189 --------------------
190 The platform re-enables MMIO to the device (but typically not the
200 link reset was performed by the HW. If the platform can't just re-enable IOs
211 such an error might cause IOs to be re-blocked for the whole
217 - PCI_ERS_RESULT_RECOVERED
226 - PCI_ERS_RESULT_NEED_RESET
231 - PCI_ERS_RESULT_DISCONNECT
243 ------------------
244 The platform resets the link. This is a PCI-Express specific step
249 ------------------
254 will be platform-dependent. Upon completion of slot reset, the
263 power-on followed by power-on BIOS/system firmware initialization.
264 Soft reset is also known as hot-reset.
281 device initialization routines, and an unusual config space setup
284 This call gives drivers the chance to re-initialize the hardware
285 (re-download firmware, etc.). At this point, the driver may assume
288 memory mapped I/O space and DMA. Interrupts (Legacy, MSI, or MSI-X)
304 Drivers for multi-function cards will need to coordinate among
305 themselves as to which driver instance will perform any "one-shot"
306 or global device initialization. For example, the Symbios sym53cxx2
309 + if (PCI_FUNC(pdev->devfn) == 0)
313 - PCI_ERS_RESULT_DISCONNECT
323 + pdev->needs_freset = 1;
331 The current powerpc implementation does not try a power-cycle
337 -------------------------
349 -------------------------
355 cancel all pending I/O, refuse all new I/O, returning -EIO to
361 permanent failure in some way. If the device is hotplug-capable,
364 caused by over-heating, some by a poorly seated card. Many
367 errors. See the discussion in Documentation/arch/powerpc/eeh-pci-error-recovery.rst
368 for additional detail on real-life experience of the causes of
373 ---------------------------
385 - There is no guarantee that interrupt delivery can proceed from any
390 - There is no guarantee that interrupt delivery is stopped, that is,
397 interrupts are routed to error-management capable slots and can deal
407 the file Documentation/arch/powerpc/eeh-pci-error-recovery.rst
413 - drivers/scsi/ipr
414 - drivers/scsi/sym53c8xx_2
415 - drivers/scsi/qla2xxx
416 - drivers/scsi/lpfc
417 - drivers/next/bnx2.c
418 - drivers/next/e100.c
419 - drivers/net/e1000
420 - drivers/net/e1000e
421 - drivers/net/ixgbe
422 - drivers/net/cxgb3
423 - drivers/net/s2io.c
429 - drivers/cxl/pci.c
432 -------