Lines Matching +full:multi +full:- +full:functional
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",
115 event will be platform-dependent, but will follow the general
119 -------------------
126 --------------------
143 - PCI_ERS_RESULT_CAN_RECOVER
148 - PCI_ERS_RESULT_NEED_RESET
151 - PCI_ERS_RESULT_DISCONNECT
158 then the platform should re-enable IOs on the slot (or do nothing in
174 Doing better requires complex multi-threaded logic in the error
188 --------------------
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
210 such an error might cause IOs to be re-blocked for the whole
216 - PCI_ERS_RESULT_RECOVERED
218 functional and thinks it is ready to start
225 - PCI_ERS_RESULT_NEED_RESET
230 - PCI_ERS_RESULT_DISCONNECT
242 ------------------
243 The platform resets the link. This is a PCI-Express specific step
248 ------------------
253 will be platform-dependent. Upon completion of slot reset, the
262 power-on followed by power-on BIOS/system firmware initialization.
263 Soft reset is also known as hot-reset.
283 This call gives drivers the chance to re-initialize the hardware
284 (re-download firmware, etc.). At this point, the driver may assume
285 that the card is in a fresh state and is fully functional. The slot
287 memory mapped I/O space and DMA. Interrupts (Legacy, MSI, or MSI-X)
303 Drivers for multi-function cards will need to coordinate among
304 themselves as to which driver instance will perform any "one-shot"
308 + if (PCI_FUNC(pdev->devfn) == 0)
312 - PCI_ERS_RESULT_DISCONNECT
322 + pdev->needs_freset = 1;
330 The current powerpc implementation does not try a power-cycle
336 -------------------------
348 -------------------------
354 cancel all pending I/O, refuse all new I/O, returning -EIO to
360 permanent failure in some way. If the device is hotplug-capable,
363 caused by over-heating, some by a poorly seated card. Many
366 errors. See the discussion in powerpc/eeh-pci-error-recovery.txt
367 for additional detail on real-life experience of the causes of
372 ---------------------------
384 - There is no guarantee that interrupt delivery can proceed from any
389 - There is no guarantee that interrupt delivery is stopped, that is,
396 interrupts are routed to error-management capable slots and can deal
406 the file Documentation/powerpc/eeh-pci-error-recovery.rst
412 - drivers/scsi/ipr
413 - drivers/scsi/sym53c8xx_2
414 - drivers/scsi/qla2xxx
415 - drivers/scsi/lpfc
416 - drivers/next/bnx2.c
417 - drivers/next/e100.c
418 - drivers/net/e1000
419 - drivers/net/e1000e
420 - drivers/net/ixgb
421 - drivers/net/ixgbe
422 - drivers/net/cxgb3
423 - drivers/net/s2io.c
426 -------