On Thu, Mar 28, 2013 at 09:31:28PM +0100, Thierry Reding wrote:
> By default these clocks are children of pll_m, but in downstream kernels
> they are reparented to pll_c. While at it, decrease their frequencies to
> 300 MHz because the defaults aren't in the specified range.
>
> gr2d can reportedly run at much higher frequencies, but 300 MHz works
> and is a more conservative default.
>
> Signed-off-by: Thierry Reding <thierry.reding@xxxxxxxxxxxxxxxxx>
> ---
> drivers/clk/tegra/clk-tegra20.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/clk/tegra/clk-tegra20.c b/drivers/clk/tegra/clk-tegra20.c
> index bf19400..b020beb 100644
> --- a/drivers/clk/tegra/clk-tegra20.c
> +++ b/drivers/clk/tegra/clk-tegra20.c
> @@ -1247,6 +1247,8 @@ static __initdata struct tegra_clk_init_table init_table[] = {
> {host1x, pll_c, 150000000, 0},
> {disp1, pll_p, 600000000, 0},
> {disp2, pll_p, 600000000, 0},
> + {gr2d, pll_c, 300000000, 0},
> + {gr3d, pll_c, 300000000, 0},
> {clk_max, clk_max, 0, 0}, /* This MUST be the last entry */
> };
>
In the end we should move to a more flexible scheme where the pll_c frequency
is determined by the needs of the various users, but for now this should do I
think.
Acked-By: Peter De Schrijver <pdeschrijver@xxxxxxxxxx>
Cheers,
Peter.
--
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
