Lines Matching refs:t

54 Power Management Interface Specification doesn't define any standard method of
257 messages sent by PCI Express endpoints integrated with the Root Complex don't
265 and if it doesn't do that, the kernel must not modify their contents.  Of course
417 callback, if defined, and if that callback doesn't return error code (or is not
422 however, the PCI subsystem doesn't really know if the device really can be
458 the device's driver doesn't provide a struct dev_pm_ops object (containing
469 devices that don't depend on each other in a known way (i.e. none of the paths
473 been called, which means that the device driver's interrupt handler won't be
477 configuration registers of the device are saved if the driver's callback hasn't
482 device's standard configuration registers haven't been saved yet (one of the
494 PCI device drivers (that don't implement legacy power management callbacks) are
545 suspend phase described above, which means that if two PCI devices don't depend
577 and it doesn't apply the suspend-related hardware quirks.  It is executed
578 asynchronously for different PCI devices that don't depend on each other in a
583 routine instead of pm->suspend_noirq().  It also doesn't attempt to prepare the
585 the device's standard configuration registers if they haven't been saved by one
610 asynchronously for different PCI devices that don't depend on each other in a
629 although they don't attempt to save the device's standard configuration
696 pci_driver are used.  The legacy approach, however, doesn't allow one to define
1070 function.  If it doesn't do that, the counter will always be different from