From: t.figa@samsung.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] ARM: Exynos: Add generic compatible string
Date: Wed, 19 Feb 2014 13:45:45 +0100 [thread overview]
Message-ID: <5304A779.1060702@samsung.com> (raw)
In-Reply-To: <1392809645-631-1-git-send-email-sachin.kamat@linaro.org>
Hi Sachin,
[adding linux-arm-kernel ML to CC list]
On 19.02.2014 12:34, Sachin Kamat wrote:
> To avoid modifying the kernel every time a new SoC variant
> comes out.
>
> Suggested-by: Arnd Bergmann <arnd@arndb.de>
> Signed-off-by: Sachin Kamat <sachin.kamat@linaro.org>
> ---
> arch/arm/mach-exynos/mach-exynos4-dt.c | 1 +
> arch/arm/mach-exynos/mach-exynos5-dt.c | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/arch/arm/mach-exynos/mach-exynos4-dt.c b/arch/arm/mach-exynos/mach-exynos4-dt.c
> index d3e54b7644d7..5d037b561253 100644
> --- a/arch/arm/mach-exynos/mach-exynos4-dt.c
> +++ b/arch/arm/mach-exynos/mach-exynos4-dt.c
> @@ -28,6 +28,7 @@ static void __init exynos4_dt_machine_init(void)
> }
>
> static char const *exynos4_dt_compat[] __initdata = {
> + "samsung,exynos4",
> "samsung,exynos4210",
> "samsung,exynos4212",
> "samsung,exynos4412",
> diff --git a/arch/arm/mach-exynos/mach-exynos5-dt.c b/arch/arm/mach-exynos/mach-exynos5-dt.c
> index 37ea261f0f6c..ad0db5a93da8 100644
> --- a/arch/arm/mach-exynos/mach-exynos5-dt.c
> +++ b/arch/arm/mach-exynos/mach-exynos5-dt.c
> @@ -50,6 +50,7 @@ static void __init exynos5_dt_machine_init(void)
> }
>
> static char const *exynos5_dt_compat[] __initdata = {
> + "samsung,exynos5",
> "samsung,exynos5250",
> "samsung,exynos5420",
> "samsung,exynos5440",
>
Since all Exynos chips can be easily recognized using dedicated chip ID
register, I wonder whether we really need to maintain two distinct board
files for Exynos 4 and 5 series, especially when both of them are doing
mostly the same set up, which can be simply generalized to cover all the
cases.
Instead of adding just another level of artificially fine grained
compatible strings, I'd rather suggest merging both board files together
and adding a single compatible string identifying all SoCs that can be
further differentiated by using hardware chip ID register.
What do you think?
P.S. Please always keep respective subsystem/arch level MLs on CC list,
in this case linux-arm-kernel. The linux-samsung-soc ML is just a
convenience tool to group all threads about Samsung SoCs, not a way to
bypass respective subsystem MLs.
Best regards,
Tomasz
next parent reply other threads:[~2014-02-19 12:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1392809645-631-1-git-send-email-sachin.kamat@linaro.org>
2014-02-19 12:45 ` Tomasz Figa [this message]
2014-02-20 4:14 ` [PATCH 1/1] ARM: Exynos: Add generic compatible string Sachin Kamat
2014-02-20 14:51 ` Tomasz Figa
2014-02-20 17:00 ` Arnd Bergmann
2014-02-20 17:34 ` Tomasz Figa
2014-02-20 17:48 ` Arnd Bergmann
2014-02-21 6:08 ` Sachin Kamat
2014-02-21 13:18 ` Tomasz Figa
2014-02-21 14:48 ` Arnd Bergmann
2014-02-21 15:21 ` Tomasz Figa
2014-02-21 15:31 ` Tomasz Figa
2014-02-24 12:03 ` Sachin Kamat
2014-02-25 0:35 ` Kukjin Kim
2014-02-25 0:52 ` Tomasz Figa
2014-02-25 1:00 ` Kukjin Kim
2014-02-25 3:03 ` Sachin Kamat
2014-02-25 4:42 ` Olof Johansson
2014-02-25 11:42 ` Arnd Bergmann
2014-03-05 8:25 ` Sachin Kamat
2014-03-05 12:12 ` Tomasz Figa
2014-03-05 15:30 ` Sachin Kamat
2014-02-24 12:02 ` Sachin Kamat
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=5304A779.1060702@samsung.com \
--to=t.figa@samsung.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).