From: Kevin Hilman <khilman@deeprootsystems.com>
To: Mike Chan <mike@android.com>
Cc: linux-omap@vger.kernel.org, Paul Walmsley <paul@pwsan.com>
Subject: Re: Future of resource framework?
Date: Fri, 21 May 2010 09:47:51 -0700 [thread overview]
Message-ID: <871vd5kxqg.fsf@deeprootsystems.com> (raw)
In-Reply-To: <AANLkTilpHjef3xbxB9QN9bj6MFmJA1jMwVxNQyZQcSKy@mail.gmail.com> (Mike Chan's message of "Thu\, 20 May 2010 15\:37\:17 -0700")
Mike Chan <mike@android.com> writes:
> I'm not sure if this has been discussed, yet but since it seems that
> the resource framework will not be making it upstream, I am curious
> what are the replacements under consideration. I am starting to see
> similar issues on other platforms (msm / tegra) so more generic
> (non-omap) solution might be something to consider.
Hi Mike,
Which parts of the SRF do you currently use and find useful? It would
be helpful for us to to understand the parts you see as useful and
potentially helpful to generalize.
As you know, the current implementation has a several layers
and attempts to manage several things: OPPs, latencies etc.
Our current plans are essentially to break up the "one framework to
rule them all" philosophy and design of SRF and manage the various
pieces by exending other layers such as the new OPP layer and voltage
layers. Latencies are being managed by the omap_device layer and we
will hopefully have some discussions with the broader linux-pm
community about generalizing that more into the generic driver model
over this year.
For the OPP management parts, you should expect RFC patches in the
next week or two that will start discussions on this.
Thanks for the input,
Kevin
next prev parent reply other threads:[~2010-05-21 16:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 22:37 Future of resource framework? Mike Chan
2010-05-20 23:23 ` Nishanth Menon
2010-05-21 16:47 ` Kevin Hilman [this message]
2010-06-03 23:31 ` Mike Chan
2010-06-03 23:52 ` Kevin Hilman
2010-06-04 0:10 ` Mike Chan
2010-06-04 3:01 ` Gadiyar, Anand
2010-06-04 10:50 ` Gopinath, Thara
2010-06-04 10:52 ` Gadiyar, Anand
2010-06-07 19:29 ` Mike Chan
2010-06-08 5:24 ` Gopinath, Thara
2010-06-07 19:31 ` Felipe Balbi
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=871vd5kxqg.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=mike@android.com \
--cc=paul@pwsan.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.