From: Bryan Huntsman <bryanh@codeaurora.org>
To: Mike Chan <mike@android.com>
Cc: linux-pm@lists.linux-foundation.org,
mark gross <640e9920@gmail.com>,
markgross@thegnar.org
Subject: Re: PM QoS dynamic resource manager
Date: Tue, 08 Jun 2010 16:03:20 -0700 [thread overview]
Message-ID: <4C0ECC38.2000003@codeaurora.org> (raw)
In-Reply-To: <AANLkTinGBvZm870CsjocsCV1SmQ-FCCbJLtKWR1juB1Q@mail.gmail.com>
>> http://lkml.org/lkml/2010/4/22/213 (I guess the details are in the
>> archives) I'm happy to re-visit it.
>>
>
> Interesting patch, it looks like having a "system wide bus" doesn't
> easily apply to msm and tegra platforms.
> An example of some things I would like to be able to control are i2c
> and memory bus.
>
> I'm tempted to suggest adding two types memory and i2c but I'm not
> sure how future proof this will be given the growing complexity in the
> embedded hardware road-map.
> What about the possibility of registering not one but several buses?
> You could add a bus qos param, with a type enum, or bind to some
> platform_driver or bus_driver
>
> Then there's the issue of having to deal with platform specific buses,
> do you add this type to pm qos with only one user? Or have some
> platform bus types defined somewhere. The generic code of min / max
> for resource X can be useful so everyone doesn't spin their own
> resource framework in their own architecture.
>
> -- Mike
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.
- Bryan
next prev parent reply other threads:[~2010-06-08 23:03 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 [this message]
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
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=4C0ECC38.2000003@codeaurora.org \
--to=bryanh@codeaurora.org \
--cc=640e9920@gmail.com \
--cc=linux-pm@lists.linux-foundation.org \
--cc=markgross@thegnar.org \
--cc=mike@android.com \
/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