On 14.11.2012 22:04, Thierry Reding wrote: > According to tegra20_clocks_data.c, the maximum clock frequency for > host1x is 166 MHz, so 216 is probably not a good idea. 150 MHz sounds > sensible, though. > > I was going to send a new version of the patch set tonight, but I'll > wait until I can test it tomorrow and once Terje has reported back that > things work fine. Hi, I tried with 150MHz, 133.3MHz, 100MHz and as an act of desperation 300MHz. None of them worked. pll_p with 216MHz seems to be the only option that works on my board. But, as said, this seems to affect only the case where nvhost is integrated, too, so your patch creates a working DRM and frame buffer, so I'm fine with leaving it as it was in the original patch set. Meanwhile, we need to figure out if we somehow misprogram PLLC or host1x clock when it's attached to PLLC on Tegra20. 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
