Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756865AbbEETf6 (ORCPT ); Tue, 5 May 2015 15:35:58 -0400 Received: from iolanthe.rowland.org ([192.131.102.54]:52006 "HELO iolanthe.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1752311AbbEETf4 (ORCPT ); Tue, 5 May 2015 15:35:56 -0400 Date: Tue, 5 May 2015 15:35:55 -0400 (EDT) From: Alan Stern X-X-Sender: stern@iolanthe.rowland.org To: Chirantan Ekbote cc: "Rafael J. Wysocki" , John Stultz , Olof Johansson , Bastien Nocera , Linux Kernel Mailing List , , Tomeu Vizoso , Linux PM list Subject: Re: A desktop environment[1] kernel wishlist In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1367 Lines: 29 On Tue, 5 May 2015, Chirantan Ekbote wrote: > This is our plan for the next version (see my email earlier in this > thread). Keeping a hybrid power state with hacks in the drivers isn't > really maintainable, scalable, or upstream-able and has caused us some > headaches already. Unfortunately we were working with the 3.14 kernel > at the time, which didn't have the framework necessary to do anything > else. The new version of lucid sleep will have the power manager > runtime suspend power-hungry devices before a suspend so that they > remain powered off at resume time. The power manager can then decide > to resume those devices based on whether the wakeup event was > user-triggered. > > Being able to determine the wakeup type from userspace is the only > functionality we need from the kernel that doesn't already exist in > mainline. Maybe you can simplify the problem. You don't really need to know the wakeup type, or to determine which device was responsible for the wakeup. All you really need to know is whether the wakeup was user-triggered. That may be much easier to discover. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/