summaryrefslogtreecommitdiffstats
path: root/arch/arm/mach-tegra/tegra2_clocks.c
diff options
context:
space:
mode:
authorAllen Martin <amartin@nvidia.com>2010-09-10 09:17:33 -0500
committerStephen Warren <swarren@nvidia.com>2012-04-25 15:22:09 -0600
commitc8b62ab41f76218efca5e4baa5c22ef52a9fe3a5 (patch)
treeb1b75cda34973167c2fddefcf8d3b807f670d57f /arch/arm/mach-tegra/tegra2_clocks.c
parentaef7704c6cc36db9618603b22194def441d30432 (diff)
downloadop-kernel-dev-c8b62ab41f76218efca5e4baa5c22ef52a9fe3a5.zip
op-kernel-dev-c8b62ab41f76218efca5e4baa5c22ef52a9fe3a5.tar.gz
ARM: tegra: Add pllc clock init table
pll_c will be used as a clock source. Fill in tegra_pll_c_freq_table[] so that it's possible to explicitly initialize the PLL. NVIDIA's downstream nv-3.1 kernel and the ChromeOS kernel have different pll_c tables. nv-3.1 contains entries for 522MHz and 598MHz output, whereas the ChromeOS kernel contains entries for 600MHz output. I chose to upstream the ChromeOS values for now, since the 600MHz rate appears to match the default rate of this PLL when the HW boots, and it's not clear to me why 522 or 598MHz are more useful. Signed-off-by: Allen Martin <amartin@nvidia.com> Signed-off-by: Olof Johansson <olofj@chromium.org> Signed-off-by: Stephen Warren <swarren@nvidia.com> [swarren: wrote commit description]
Diffstat (limited to 'arch/arm/mach-tegra/tegra2_clocks.c')
-rw-r--r--arch/arm/mach-tegra/tegra2_clocks.c4
1 files changed, 4 insertions, 0 deletions
diff --git a/arch/arm/mach-tegra/tegra2_clocks.c b/arch/arm/mach-tegra/tegra2_clocks.c
index 592a4ee..a357ad2 100644
--- a/arch/arm/mach-tegra/tegra2_clocks.c
+++ b/arch/arm/mach-tegra/tegra2_clocks.c
@@ -1486,6 +1486,10 @@ static struct clk tegra_clk_m = {
};
static struct clk_pll_freq_table tegra_pll_c_freq_table[] = {
+ { 12000000, 600000000, 600, 12, 1, 8 },
+ { 13000000, 600000000, 600, 13, 1, 8 },
+ { 19200000, 600000000, 500, 16, 1, 6 },
+ { 26000000, 600000000, 600, 26, 1, 8 },
{ 0, 0, 0, 0, 0, 0 },
};
OpenPOWER on IntegriCloud