On 8 August 2013 00:20, Stephen Warren <swarren@xxxxxxxxxxxxx> wrote: > Right, and that's *exactly* what having a cpufreq driver is for; to > implement the details of CPU clock management. cpufreq drivers used to keep such information since a long time, probably because there wasn't another place to keep them and provide generic API's (like generic clock framework).. And so this replication started to get in place which we are trying to get rid of now. All cpufreq drivers share a lot of common code which can go away and so cpufreq-cpu0 was introduced.. With this patchset this replication goes away for tegra atleast at the cost of a platform specific clk-cpu driver.. I think that's a good deal, isn't it? And that's the only way you can use these generic drivers that we have... -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
