[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.1005061007050.1708-100000@iolanthe.rowland.org>
Date: Thu, 6 May 2010 10:08:14 -0400 (EDT)
From: Alan Stern <stern@...land.harvard.edu>
To: Brian Swetland <swetland@...gle.com>
cc: Kevin Hilman <khilman@...prootsystems.com>,
Matthew Garrett <mjg@...hat.com>,
Mark Brown <broonie@...nsource.wolfsonmicro.com>,
"Rafael J. Wysocki" <rjw@...k.pl>,
Arve Hjønnevåg <arve@...roid.com>,
<linux-pm@...ts.linux-foundation.org>,
<linux-kernel@...r.kernel.org>, Tejun Heo <tj@...nel.org>,
Oleg Nesterov <oleg@...hat.com>,
Paul Walmsley <paul@...an.com>, <magnus.damm@...il.com>,
mark gross <mgross@...ux.intel.com>,
Arjan van de Ven <arjan@...radead.org>,
Geoff Smith <geoffx.smith@...el.com>
Subject: Re: [PATCH 0/8] Suspend block api (version 6)
On Wed, 5 May 2010, Brian Swetland wrote:
> > Probably generalizing these into the LDM is the direction to go so
> > userspace can set constraints on a per-device (or per-class?) basis:
> >
> > /sys/devices/.../power/constraint/throughput
> > /sys/devices/.../power/constraint/wakeup_latency
> > /sys/devices/.../power/constraint/... ?
>
> The constraint stuff is definitely something I'd love to talk about in
> detail. It's a problem that I think is common to every SoC I've
> worked with. Having a general solution for this problem (of
> specifying and observing various constraints for clock, power, qos,
> etc) kernel-wide would seem like a big win.
>
> Might be worth kicking some design ideas around and getting a bunch of
> the interested parties together at some of the upcoming linux
> conference things this fall on the east coast?
The Linux Power-Management Summit is scheduled for August 9, at the
start of the LinuxCon meeting in Boston. This would make an excellent
topic for discussion.
Alan Stern
--
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