Lines Matching full:routine

450 The pci_pm_prepare() routine first puts the device into the "fully functional"
455 The pci_pm_suspend() routine first checks if the device's driver implements
462 bridges are ignored by this routine).  Next, the device driver's pm->suspend()
472 The pci_pm_suspend_noirq() routine is executed after suspend_device_irqs() has
474 invoked while this routine is running.  It first checks if the device's driver
476 late suspend routine is called and its result is returned (the standard
479 present, the device's standard configuration registers are saved and the routine
520 The pci_pm_resume_noirq() routine first puts the device into the full-power
534 The pci_pm_resume() routine first checks if the device's standard configuration
546 on each other in a known way, the pci_pm_resume() routine may be executed for
549 The pci_pm_complete() routine only executes the device driver's pm->complete()
575 The pci_pm_freeze() routine is quite similar to pci_pm_suspend(), but it runs
581 The pci_pm_freeze_noirq() routine, in turn, is similar to
583 routine instead of pm->suspend_noirq().  It also doesn't attempt to prepare the
608 The pci_pm_thaw() routine is similar to pci_pm_resume(), but it runs the device
974 3.1.18. Pointing Multiple Callback Pointers to One Routine
979 point two or more members of struct dev_pm_ops to the same routine.  There are
983 suspend routine pointed to by the .suspend(), .freeze(), and .poweroff()
984 members and one resume routine pointed to by the .resume(), .thaw(), and
993 dev_pm_ops to indicate that one suspend routine is to be pointed to by the
994 .suspend(), .freeze(), and .poweroff() members and one resume routine is to
1075 from its probe routine to make runtime PM work for the device.