Re: [PATCH] OMAP: Cpufreq: Clean up to support multi omap builds

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* Thara Gopinath <thara@xxxxxx> [110105 08:23]:
> +#define OMAP1_MPU_CLK		"mpu"
> +#define OMAP2_MPU_CLK		"virt_prcm_set"
> +#define OMAP3_MPU_CLK		"dpll1_ck"
...
  
>  static int __init omap_cpufreq_init(void)
>  {
> +	if (cpu_class_is_omap1()) {
> +		mpu_clk_name = OMAP1_MPU_CLK;
> +		arch_cpu_init = omap1_cpu_init;
> +		arch_cpu_target = omap1_cpu_target;
> +	} else if (cpu_is_omap24xx()) {
> +		mpu_clk_name = OMAP2_MPU_CLK;
> +		arch_cpu_init = omap1_cpu_init;
> +		arch_cpu_target = omap2plus_cpu_target;
> +	} else if (cpu_is_omap34xx()) {
> +		mpu_clk_name = OMAP3_MPU_CLK;
> +		arch_cpu_init = omap3_cpu_init;
> +		arch_cpu_target = omap2plus_cpu_target;
> +	} else {
> +		pr_warning("%s: cpufreq support not yet added\n", __func__);
> +		return -EINVAL;
> +	}
> +

To me it seems that you should be able to now remove these
just by adding the mpu clock alias to the struct omap_clk
tables?

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux