linux-kernel - Re: [PATCH 1/2] PM / Runtime: Add sysfs switch for disabling device run-time PM (rev. 2)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 23 Jan 2010 21:08:07 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Alan Stern <stern@...land.harvard.edu>
Cc:	pm list <linux-pm@...ts.linux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Matthew Garrett <mjg59@...f.ucam.org>, Greg KH <greg@...ah.com>
Subject: Re: [PATCH 1/2] PM / Runtime: Add sysfs switch for disabling device run-time PM (rev. 2)

On Saturday 23 January 2010, Alan Stern wrote:
> On Sat, 23 Jan 2010, Rafael J. Wysocki wrote:
> 
> > Hmm, OK.
> > 
> > Of course, if the driver decides to leave disable_depth > 0, the user still
> > won't be able to do anything about that, but if I understand correctly, you
> > want drivers to have the option to use pm_runtime_forbid() initially, right
> > after pm_runtime_enable(), so that the user space can turn the runtime PM
> > on if desired via sysfs.
> > 
> > That makes sense.  I have a usage case for that myself. :-)
> > 
> > Updated patch is appended.
> 
> It looks good.
> 
> Acked-by: Alan Stern <stern@...land.harvard.edu>

Thanks!

Rafael
--
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/