Home
last modified time | relevance | path

Searched hist:c043c025 (Results 1 – 8 of 8) sorted by relevance

/openbmc/u-boot/arch/arm/include/asm/arch-tegra210/
H A Dclock-tables.hc043c025 Thu Aug 20 04:42:19 CDT 2015 Thierry Reding <treding@nvidia.com> ARM: tegra: Implement clk_m

On currently supported SoCs, clk_m always runs at the same frequency as
the oscillator input. However newer SoC generations such as Tegra210 no
longer have that restriction. Prepare for that by separating clk_m from
the oscillator clock and allow SoC code to override the clk_m rate.

Signed-off-by: Thierry Reding <treding@nvidia.com>
Signed-off-by: Tom Warren <twarren@nvidia.com>
/openbmc/u-boot/arch/arm/include/asm/arch-tegra114/
H A Dclock-tables.hc043c025 Thu Aug 20 04:42:19 CDT 2015 Thierry Reding <treding@nvidia.com> ARM: tegra: Implement clk_m

On currently supported SoCs, clk_m always runs at the same frequency as
the oscillator input. However newer SoC generations such as Tegra210 no
longer have that restriction. Prepare for that by separating clk_m from
the oscillator clock and allow SoC code to override the clk_m rate.

Signed-off-by: Thierry Reding <treding@nvidia.com>
Signed-off-by: Tom Warren <twarren@nvidia.com>
/openbmc/u-boot/arch/arm/include/asm/arch-tegra30/
H A Dclock-tables.hc043c025 Thu Aug 20 04:42:19 CDT 2015 Thierry Reding <treding@nvidia.com> ARM: tegra: Implement clk_m

On currently supported SoCs, clk_m always runs at the same frequency as
the oscillator input. However newer SoC generations such as Tegra210 no
longer have that restriction. Prepare for that by separating clk_m from
the oscillator clock and allow SoC code to override the clk_m rate.

Signed-off-by: Thierry Reding <treding@nvidia.com>
Signed-off-by: Tom Warren <twarren@nvidia.com>
/openbmc/u-boot/arch/arm/include/asm/arch-tegra124/
H A Dclock-tables.hc043c025 Thu Aug 20 04:42:19 CDT 2015 Thierry Reding <treding@nvidia.com> ARM: tegra: Implement clk_m

On currently supported SoCs, clk_m always runs at the same frequency as
the oscillator input. However newer SoC generations such as Tegra210 no
longer have that restriction. Prepare for that by separating clk_m from
the oscillator clock and allow SoC code to override the clk_m rate.

Signed-off-by: Thierry Reding <treding@nvidia.com>
Signed-off-by: Tom Warren <twarren@nvidia.com>
/openbmc/u-boot/arch/arm/include/asm/arch-tegra20/
H A Dclock-tables.hc043c025 Thu Aug 20 04:42:19 CDT 2015 Thierry Reding <treding@nvidia.com> ARM: tegra: Implement clk_m

On currently supported SoCs, clk_m always runs at the same frequency as
the oscillator input. However newer SoC generations such as Tegra210 no
longer have that restriction. Prepare for that by separating clk_m from
the oscillator clock and allow SoC code to override the clk_m rate.

Signed-off-by: Thierry Reding <treding@nvidia.com>
Signed-off-by: Tom Warren <twarren@nvidia.com>
/openbmc/u-boot/arch/arm/mach-tegra/tegra210/
H A Dclock.cc043c025 Thu Aug 20 04:42:19 CDT 2015 Thierry Reding <treding@nvidia.com> ARM: tegra: Implement clk_m

On currently supported SoCs, clk_m always runs at the same frequency as
the oscillator input. However newer SoC generations such as Tegra210 no
longer have that restriction. Prepare for that by separating clk_m from
the oscillator clock and allow SoC code to override the clk_m rate.

Signed-off-by: Thierry Reding <treding@nvidia.com>
Signed-off-by: Tom Warren <twarren@nvidia.com>
/openbmc/u-boot/arch/arm/mach-tegra/
H A Dclock.cc043c025 Thu Aug 20 04:42:19 CDT 2015 Thierry Reding <treding@nvidia.com> ARM: tegra: Implement clk_m

On currently supported SoCs, clk_m always runs at the same frequency as
the oscillator input. However newer SoC generations such as Tegra210 no
longer have that restriction. Prepare for that by separating clk_m from
the oscillator clock and allow SoC code to override the clk_m rate.

Signed-off-by: Thierry Reding <treding@nvidia.com>
Signed-off-by: Tom Warren <twarren@nvidia.com>
/openbmc/u-boot/arch/arm/include/asm/arch-tegra/
H A Dclock.hc043c025 Thu Aug 20 04:42:19 CDT 2015 Thierry Reding <treding@nvidia.com> ARM: tegra: Implement clk_m

On currently supported SoCs, clk_m always runs at the same frequency as
the oscillator input. However newer SoC generations such as Tegra210 no
longer have that restriction. Prepare for that by separating clk_m from
the oscillator clock and allow SoC code to override the clk_m rate.

Signed-off-by: Thierry Reding <treding@nvidia.com>
Signed-off-by: Tom Warren <twarren@nvidia.com>