Lines Matching full:might

84 synergies exist, so that several drivers using runtime PM might put the system
244 For simple drivers, suspend might quiesce the device using class code
249 More power-aware drivers might prepare the devices for triggering system wakeup
405 	vectors, like PCI, generally need it; otherwise a driver might encounter
420 might identify GPIO signals hooked up to a switch or other external hardware,
485 the end of resume might not be the one which preceded suspension.
592 Although in principle the image might be loaded into memory and the
666 Device low-power states aren't standard.  One device might only handle
667 "on" and "off", while another might support a dozen different versions of
679 might be able to treat DMA completion as a wakeup event (sometimes DMA can stay
685 its frame buffer might even be updated by a DSP or other non-Linux CPU while
689 One target system state might allow a given device to be very operational;
690 another might require a hard shut down with re-initialization on resume.
691 And two different target systems might use the same device in different
692 ways; the aforementioned LCD might be active in one product's "standby",
693 but a different product using the same SOC might work differently.
747 often support a range of runtime power states, which might use names such