Lines Matching refs:drivers

23 between the affected device drivers and the PCI controller chip.
24 This document describes a generic API for notifying device drivers
30 is reported as soon as possible to all affected device drivers,
32 cards. This allows device drivers to avoid deadlocking in spinloops,
34 It also gives the drivers a chance to defer incoming I/O as
39 devices that have multiple device drivers associated with them.
46 After a reset and/or a re-enabling of I/O, all drivers are
60 device drivers already handle very similar recovery procedures;
137 All drivers participating in this system must implement this call.
151 drivers.
153 If all drivers on the segment/slot return PCI_ERS_RESULT_CAN_RECOVER,
185 device drivers.
192 all drivers on a segment agree that they can try to recover and if no automatic
226 The next step taken depends on the results returned by the drivers.
227 If all drivers returned PCI_ERS_RESULT_RECOVERED, then the platform
236 on all affected device drivers.  This is a PCI-Express specific state
245 will call resume() once all drivers have ack'd link_reset().
291 This call gives drivers the chance to re-initialize the hardware
299 at this point.  If all device drivers report success on this
344 drivers if all drivers on the segment have returned
380 no slot reset capability may want to just "ignore" drivers that can't
412 >>> As of this writing, there is a growing list of device drivers with
416 >>> drivers/scsi/ipr
417 >>> drivers/scsi/sym53c8xx_2
418 >>> drivers/scsi/qla2xxx
419 >>> drivers/scsi/lpfc
420 >>> drivers/next/bnx2.c
421 >>> drivers/next/e100.c
422 >>> drivers/net/e1000
423 >>> drivers/net/e1000e
424 >>> drivers/net/ixgb
425 >>> drivers/net/ixgbe
426 >>> drivers/net/cxgb3
427 >>> drivers/net/s2io.c
428 >>> drivers/net/qlge