From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751997AbZH1HBj (ORCPT ); Fri, 28 Aug 2009 03:01:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751727AbZH1HBh (ORCPT ); Fri, 28 Aug 2009 03:01:37 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:56598 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751478AbZH1HBh (ORCPT ); Fri, 28 Aug 2009 03:01:37 -0400 Date: Fri, 28 Aug 2009 09:01:25 +0200 From: Pavel Machek To: "Rafael J. Wysocki" Cc: Dmitry Torokhov , linux-pm , LKML , Len Brown , Alan Stern , ACPI Devel Maling List , Arjan van de Ven , Zhang Rui , Linux PCI Subject: Re: [PATCH 8] PM: Allow user space to change the power.async_suspend flag of devices Message-ID: <20090828070124.GB27928@elf.ucw.cz> References: <200908262217.19609.rjw@sisk.pl> <200908272120.56021.rjw@sisk.pl> <20090827203634.372EC526EC9@mailhub.coreip.homeip.net> <200908280024.06082.rjw@sisk.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200908280024.06082.rjw@sisk.pl> X-Warning: Reading this can be dangerous to your mental health. User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri 2009-08-28 00:24:06, Rafael J. Wysocki wrote: > On Thursday 27 August 2009, Dmitry Torokhov wrote: > > Hi Rafael, > > > > On Thu, Aug 27, 2009 at 09:20:55PM +0200, Rafael J. Wysocki wrote: > > > From: Rafael J. Wysocki > > > > > > Add sysfs attribute power/async for every device allowing the user > > > space to access the device's power.async_suspend flag and modify it, > > > if necessary. > > > > > > > I don't think we should let users meddle with individual devices; > > one global flag should be enough to work around "broken-at-the-moment" > > issues. > > Well, this patch is handy for testing if anyone is interested, so I posted it. > > It isn't exactly safe, though, you're right. I guess it would be acceptable to let the users disable it per-driver... but if we can get without that, it would be better. (it is obviously ok for debugging). Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html