Chanwoo Choi wrote:
>
> This patch add Exynos4415's SoC ID.
>
Since the CPU ID has been removed as per comments, need to update the commit
message accordingly.
> Exynos4415 is based on the 32-bit RISC
> processor for Smartphone. Exynos4415 uses Cortex A9 quad-cores and has a target
> speed of 1.6GHz and provides 8.5GB/s memory bandwidth.
>
> Cc: Kukjin Kim <kgene.kim@xxxxxxxxxxx>
> Signed-off-by: Chanwoo Choi <cw00.choi@xxxxxxxxxxx>
> Acked-by: Kyungmin Park <kyungmin.park@xxxxxxxxxxx>
> ---
> arch/arm/mach-exynos/Kconfig | 5 +++++
> arch/arm/mach-exynos/exynos.c | 2 ++
> 2 files changed, 7 insertions(+)
>
> diff --git a/arch/arm/mach-exynos/Kconfig b/arch/arm/mach-exynos/Kconfig
> index 46f3c0d..349c867 100644
> --- a/arch/arm/mach-exynos/Kconfig
> +++ b/arch/arm/mach-exynos/Kconfig
> @@ -75,6 +75,11 @@ config SOC_EXYNOS4412
> default y
> depends on ARCH_EXYNOS4
>
> +config SOC_EXYNOS4415
> + bool "SAMSUNG EXYNOS4415"
> + default y
> + depends on ARCH_EXYNOS4
> +
I think, this is not required more...
Thanks,
Kukjin
> config SOC_EXYNOS5250
> bool "SAMSUNG EXYNOS5250"
> default y
> diff --git a/arch/arm/mach-exynos/exynos.c b/arch/arm/mach-exynos/exynos.c
> index 1b46460..1da531f 100644
> --- a/arch/arm/mach-exynos/exynos.c
> +++ b/arch/arm/mach-exynos/exynos.c
> @@ -252,6 +252,7 @@ static const struct of_device_id exynos_dt_pmu_match[] = {
> { .compatible = "samsung,exynos4210-pmu" },
> { .compatible = "samsung,exynos4212-pmu" },
> { .compatible = "samsung,exynos4412-pmu" },
> + { .compatible = "samsung,exynos4415-pmu" },
> { .compatible = "samsung,exynos5250-pmu" },
> { .compatible = "samsung,exynos5260-pmu" },
> { .compatible = "samsung,exynos5410-pmu" },
> @@ -359,6 +360,7 @@ static char const *exynos_dt_compat[] __initconst = {
> "samsung,exynos4210",
> "samsung,exynos4212",
> "samsung,exynos4412",
> + "samsung,exynos4415",
> "samsung,exynos5",
> "samsung,exynos5250",
> "samsung,exynos5260",
> --
> 1.8.5.5
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
