[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1443529760-17612-1-git-send-email-tomeu.vizoso@collabora.com>
Date: Tue, 29 Sep 2015 14:29:18 +0200
From: Tomeu Vizoso <tomeu.vizoso@...labora.com>
To: linux-pm@...r.kernel.org, Alan Stern <stern@...land.harvard.edu>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
martyn.welch@...labora.co.uk
Cc: Tomeu Vizoso <tomeu.vizoso@...labora.com>,
linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
Len Brown <len.brown@...el.com>,
Kevin Hilman <khilman@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Pavel Machek <pavel@....cz>,
Ulf Hansson <ulf.hansson@...aro.org>
Subject: [PATCH v5 0/2]
Hi,
this is v5 of an attempt to make it easier for devices to remain in
runtime PM when the system goes to sleep, mainly to reduce the time
spent resuming devices.
For this, we interpret the absence of all PM callback implementations as
it being safe to do direct_complete, so their ancestors aren't prevented
from remaining runtime-suspended.
Additionally, the prepare() callback of USB devices will return 1 if
runtime PM is enabled and the current wakeup settings are correct.
With these changes, a uvcvideo device (for example) stays in runtime
suspend when the system goes to sleep and is left in that state when the
system resumes, not delaying it unnecessarily.
Thanks,
Tomeu
Changes in v5:
- Check for all dev_pm_ops instances associated to a device, updating a
no_pm_callbacks flag at the times when that could change.
Tomeu Vizoso (2):
PM / sleep: Go direct_complete if driver has no callbacks
USB / PM: Allow USB devices to remain runtime-suspended when sleeping
drivers/base/dd.c | 3 ++
drivers/base/power/domain.c | 5 ++++
drivers/base/power/main.c | 69 ++++++++++++++++++++++++++++++++-------------
drivers/base/power/power.h | 2 ++
drivers/usb/core/port.c | 6 ++++
drivers/usb/core/usb.c | 11 +++++++-
include/linux/pm.h | 1 +
7 files changed, 77 insertions(+), 20 deletions(-)
--
2.4.3
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists