On 08.10.2013 10:53, Peter De Schrijver wrote: > On Mon, Oct 07, 2013 at 04:53:44PM +0200, Thierry Reding wrote: >> What's wrong with pll_c? We've used it for Tegra20 and Tegra30 and I >> have at least tested that gr2d works properly with it. It will also >> cause both host1x and gr2d to run off the same clock, which I guess may >> not matter at all. > Using pll_c2 is consistent with our policy in downstream. It allows more > freedom in scaling gr2d independently from host1x. host1x really should be on a clock that is not scaled. This is because it has some registers that need to be calibrated to the clock rate. It's a pain to recalibrate whenever clock rate is modified. This is why host1x is on PLLP downstream. 2D on the other hand (and all clients) is a prime candidate for clock scaling. This all is of course just hypothetical as long as we don't really scale host1x' or its clients' clocks. Terje -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
