From: Kevin Hilman <khilman@deeprootsystems.com>
To: markgross@thegnar.org
Cc: mark gross <640e9920@gmail.com>, linux-pm@lists.linux-foundation.org
Subject: Re: PM QoS dynamic resource manager
Date: Fri, 11 Jun 2010 19:42:46 +0530 [thread overview]
Message-ID: <1276265566.8214.2.camel@localhost> (raw)
In-Reply-To: <20100609030525.GD26668@gvim.org>
On Tue, 2010-06-08 at 20:05 -0700, mark gross wrote:
> On Tue, Jun 08, 2010 at 04:03:20PM -0700, Bryan Huntsman wrote:
> >
> > Mike, one idea I'm exploring is having platform-specific busses with
> > QoS constraints specified via runtime_pm as part of the LDM. Adding
> > dynamic class creation within pm_qos, or a type enum as you suggest,
> > would work. However, I think this kind of behavior would fit nicely
> > within runtime_pm.
> >
>
> Something like that is what Kevin Hilman was thinking too. It would
> bring a qos concept to the LDM for each bus driver object.
Yes, I definitely have some thoughts/ideas in this direction and is what
we are doing on OMAP. I've been on the road, so I will chime in more on
this next week when I get back...
Kevin
next prev parent reply other threads:[~2010-06-11 14:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 21:37 PM QoS dynamic resource manager Chidambaram, Praveen
2010-05-25 14:52 ` mark gross
2010-05-25 16:19 ` Chidambaram, Praveen
2010-06-08 0:18 ` Mike Chan
2010-06-08 3:33 ` mark gross
2010-06-08 14:44 ` Chidambaram, Praveen
2010-06-09 2:55 ` mark gross
2010-06-08 18:58 ` Mike Chan
2010-06-08 23:03 ` Bryan Huntsman
2010-06-08 23:35 ` Mike Chan
2010-06-08 23:48 ` Bryan Huntsman
2010-06-09 3:05 ` mark gross
2010-06-10 0:53 ` Mike Chan
2010-06-10 1:22 ` Bryan Huntsman
2010-06-11 13:55 ` mark gross
2010-06-11 14:12 ` Kevin Hilman [this message]
2010-06-17 22:32 ` Kevin Hilman
2010-06-18 5:57 ` Huntsman, Bryan
2010-06-22 23:34 ` mark gross
2010-07-18 12:57 ` mark gross
2010-07-18 15:03 ` James Bottomley
2010-07-19 1:46 ` Rafael J. Wysocki
2010-07-19 6:38 ` James Bottomley
2010-07-19 13:50 ` Matthew Garrett
2010-08-10 16:24 ` Kevin Hilman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1276265566.8214.2.camel@localhost \
--to=khilman@deeprootsystems.com \
--cc=640e9920@gmail.com \
--cc=linux-pm@lists.linux-foundation.org \
--cc=markgross@thegnar.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox