/openbmc/u-boot/arch/arm/include/asm/arch-tegra210/ |
H A D | clock-tables.h | c043c025 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 D | clock-tables.h | c043c025 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 D | clock-tables.h | c043c025 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 D | clock-tables.h | c043c025 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 D | clock-tables.h | c043c025 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 D | clock.c | c043c025 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 D | clock.c | c043c025 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 D | clock.h | c043c025 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>
|