Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754555Ab0GAPJA (ORCPT ); Thu, 1 Jul 2010 11:09:00 -0400 Received: from ist.d-labs.de ([213.239.218.44]:35586 "EHLO mx01.d-labs.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752159Ab0GAPI6 (ORCPT ); Thu, 1 Jul 2010 11:08:58 -0400 Date: Thu, 1 Jul 2010 17:08:04 +0200 From: Florian Mickler To: Pavel Machek Cc: "Rafael J. Wysocki" , linux-pm@lists.linux-foundation.org, Alan Stern , Linux Kernel Mailing List , Neil Brown , Matthew Garrett , mark gross <640e9920@gmail.com>, Arve Hj??nnev??g , Dmitry Torokhov , linux-pci@vger.kernel.org, Jesse Barnes Subject: Re: [PATCH] PM: Make it possible to avoid wakeup events from being lost Message-ID: <20100701170804.687d9604@schatten.dmk.lab> In-Reply-To: <20100701133208.GA1285@ucw.cz> References: <201006261514.13491.rjw@sisk.pl> <20100701133208.GA1285@ucw.cz> X-Mailer: Claws Mail 3.7.5 (GTK+ 2.18.9; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1449 Lines: 37 On Thu, 1 Jul 2010 15:32:08 +0200 Pavel Machek wrote: > Hi! > > > @@ -114,3 +114,17 @@ Description: > > if this file contains "1", which is the default. It may be > > disabled by writing "0" to this file, in which case all devices > > will be suspended and resumed synchronously. > > + > > +What: /sys/power/wakeup_count > > +Date: July 2010 > > +Contact: Rafael J. Wysocki > > +Description: > > + The /sys/power/wakeup_count file allows user space to avoid > > + losing wakeup events when transitioning the system into a sleep > > + state. Reading from it returns the current number of registered > > + wakeup events and it blocks if some wakeup events are being > > + processed at the time the file is read from. Writing to it > > + will only succeed if the current number of wakeup events is > > + equal to the written value and, if successful, will make the > > + kernel abort a subsequent transition to a sleep state if any > > + wakeup events are reported after the write has returned. > I can't say I quite like the way two sysfs files interact with each > other, but it is certainly better then wakelocks... What two files? Cheers, Flo -- 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/