Mike Chan <mike@xxxxxxxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
