From: Tomasz Figa <t.figa@samsung.com>
To: Sachin Kamat <sachin.kamat@linaro.org>,
linux-samsung-soc@vger.kernel.org
Cc: kgene.kim@samsung.com, patches@linaro.org
Subject: Re: [PATCH 1/1] ARM: EXYNOS: Consolidate CPU init code
Date: Fri, 21 Feb 2014 17:45:34 +0100 [thread overview]
Message-ID: <530782AE.4060500@samsung.com> (raw)
In-Reply-To: <1390391342-4344-1-git-send-email-sachin.kamat@linaro.org>
Hi Sachin,
On 22.01.2014 12:49, Sachin Kamat wrote:
> cpu_table was used to distinguish between different Exynos4 and 5 SoCs
> and assign the the initialization and io mapping pointers based on type.
> exynos_init is dummy and no longer needed as we do a DT based booting.
> By having a common io mapping function we can get rid of the whole
> table and avoid populating it for every SoC.
>
> Tested on Exynos4210, 5250 and 5420 based boards.
>
> Signed-off-by: Sachin Kamat <sachin.kamat@linaro.org>
> ---
> arch/arm/mach-exynos/common.c | 93 ++++++++---------------------------------
> 1 file changed, 17 insertions(+), 76 deletions(-)
On Exynos4412-based Trats2 board:
Tested-by: Tomasz Figa <t.figa@samsung.com>
However, please see one minor comment inline.
> diff --git a/arch/arm/mach-exynos/common.c b/arch/arm/mach-exynos/common.c
> index f18be40e5b21..02d0aaa7af59 100644
> --- a/arch/arm/mach-exynos/common.c
> +++ b/arch/arm/mach-exynos/common.c
> @@ -48,55 +48,7 @@
> #define L2_AUX_VAL 0x7C470001
> #define L2_AUX_MASK 0xC200ffff
>
> -static const char name_exynos4210[] = "EXYNOS4210";
> -static const char name_exynos4212[] = "EXYNOS4212";
> -static const char name_exynos4412[] = "EXYNOS4412";
> -static const char name_exynos5250[] = "EXYNOS5250";
> -static const char name_exynos5420[] = "EXYNOS5420";
> -static const char name_exynos5440[] = "EXYNOS5440";
> -
> -static void exynos4_map_io(void);
> -static void exynos5_map_io(void);
> -static int exynos_init(void);
> -
> -static struct cpu_table cpu_ids[] __initdata = {
> - {
> - .idcode = EXYNOS4210_CPU_ID,
> - .idmask = EXYNOS4_CPU_MASK,
> - .map_io = exynos4_map_io,
> - .init = exynos_init,
> - .name = name_exynos4210,
> - }, {
> - .idcode = EXYNOS4212_CPU_ID,
> - .idmask = EXYNOS4_CPU_MASK,
> - .map_io = exynos4_map_io,
> - .init = exynos_init,
> - .name = name_exynos4212,
> - }, {
> - .idcode = EXYNOS4412_CPU_ID,
> - .idmask = EXYNOS4_CPU_MASK,
> - .map_io = exynos4_map_io,
> - .init = exynos_init,
> - .name = name_exynos4412,
> - }, {
> - .idcode = EXYNOS5250_SOC_ID,
> - .idmask = EXYNOS5_SOC_MASK,
> - .map_io = exynos5_map_io,
> - .init = exynos_init,
> - .name = name_exynos5250,
> - }, {
> - .idcode = EXYNOS5420_SOC_ID,
> - .idmask = EXYNOS5_SOC_MASK,
> - .map_io = exynos5_map_io,
> - .init = exynos_init,
> - .name = name_exynos5420,
> - }, {
> - .idcode = EXYNOS5440_SOC_ID,
> - .idmask = EXYNOS5_SOC_MASK,
> - .init = exynos_init,
> - .name = name_exynos5440,
> - },
> -};
> +static void exynos_map_io(void);
cosmetic: Instead of adding forward declaration, the resulting
exynos_map_io() function could be simply merged with exynos_init_io().
Best regards,
Tomasz
prev parent reply other threads:[~2014-02-21 16:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 11:49 [PATCH 1/1] ARM: EXYNOS: Consolidate CPU init code Sachin Kamat
2014-02-21 16:45 ` Tomasz Figa [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=530782AE.4060500@samsung.com \
--to=t.figa@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=patches@linaro.org \
--cc=sachin.kamat@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.