From: Kukjin Kim <kgene.kim@samsung.com>
To: Sachin Kamat <sachin.kamat@linaro.org>
Cc: Tomasz Figa <t.figa@samsung.com>, Arnd Bergmann <arnd@arndb.de>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Mark Rutland <Mark.Rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Kukjin Kim <kgene.kim@samsung.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Rob Herring <robh+dt@kernel.org>,
Grant Likely <grant.likely@secretlab.ca>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
Olof Johansson <olof@lixom.net>
Subject: Re: [PATCH 1/1] ARM: Exynos: Add generic compatible string
Date: Tue, 25 Feb 2014 09:35:35 +0900 [thread overview]
Message-ID: <530BE557.20106@samsung.com> (raw)
In-Reply-To: <CAK9yfHxiHkrf1xmSFbfoKqFFSCU6w4QqwPnQNdv1m1PGtrwsLQ@mail.gmail.com>
On 02/24/14 21:03, Sachin Kamat wrote:
> On 21 February 2014 21:01, Tomasz Figa<t.figa@samsung.com> wrote:
>> On 21.02.2014 16:21, Tomasz Figa wrote:
>>>
>>> On 21.02.2014 15:48, Arnd Bergmann wrote:
>>>>
>>>> On Friday 21 February 2014 14:18:49 Tomasz Figa wrote:
>>>>>
>>>>>
>>>>>> Now that we have a broader agreement on this, I think we can go
>>>>>> ahead with the
>>>>>> following steps as an initial approach:
>>>>>> 1. Have a common machine file for both exynos4 and 5 files,
>>>>>> mach-exynos-dt.c.
>>>>>> 2. Introduce a generic compatible string "samsung,exynos".
Well, I think, we need to consider to use compatible string
"samsung,exynos" again because "exynos" name can be used on ARMv8 as
well and I don't want to say that generic/common something is always
good. So IMHO still using exynos4 and exynos5 would be better.
>>>>>> 3. Append this to the compatible property list for existing boards.
>>>>>>
>>>>>> If this plan looks OK, I can send across patches doing this.
>>>>>>
>>>>>
>>>>> Looks good. I would also merge common.c with this resulting
>>>>> mach-exynos-dt.c, as it would be the only user of the code there.
>>>>
>>>>
>>>> Sounds good. While the naming is not important, I would just call the
>>>> file 'exynos.c', in line with some of the other platforms we have.
>>>> Both the 'mach-' and the '-dt' part of the file name are redundant.
>>>>
>>>> Alternatively, you could merge it all into common.c.
>>>
>>>
>>> exynos.c sounds good to me.
>>
Well, let me see common.c and mach-exynos.c, one is for SoC specific
stuff and the other is for Board specific so I think, keeping current
file would be good, we can change the file name mach-exynos.c or
board-exynos.c though.
Thanks,
Kukjin
>>
>> One minor thing. It might be a good idea to base on top of my PM
>> consolidation part 2 series, to avoid merge conflicts:
>>
>> http://thread.gmane.org/gmane.linux.ports.arm.kernel/299340
>>
>> It should hit Kgene's tree this weekend.
>
> Sure.
>
WARNING: multiple messages have this Message-ID (diff)
From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] ARM: Exynos: Add generic compatible string
Date: Tue, 25 Feb 2014 09:35:35 +0900 [thread overview]
Message-ID: <530BE557.20106@samsung.com> (raw)
In-Reply-To: <CAK9yfHxiHkrf1xmSFbfoKqFFSCU6w4QqwPnQNdv1m1PGtrwsLQ@mail.gmail.com>
On 02/24/14 21:03, Sachin Kamat wrote:
> On 21 February 2014 21:01, Tomasz Figa<t.figa@samsung.com> wrote:
>> On 21.02.2014 16:21, Tomasz Figa wrote:
>>>
>>> On 21.02.2014 15:48, Arnd Bergmann wrote:
>>>>
>>>> On Friday 21 February 2014 14:18:49 Tomasz Figa wrote:
>>>>>
>>>>>
>>>>>> Now that we have a broader agreement on this, I think we can go
>>>>>> ahead with the
>>>>>> following steps as an initial approach:
>>>>>> 1. Have a common machine file for both exynos4 and 5 files,
>>>>>> mach-exynos-dt.c.
>>>>>> 2. Introduce a generic compatible string "samsung,exynos".
Well, I think, we need to consider to use compatible string
"samsung,exynos" again because "exynos" name can be used on ARMv8 as
well and I don't want to say that generic/common something is always
good. So IMHO still using exynos4 and exynos5 would be better.
>>>>>> 3. Append this to the compatible property list for existing boards.
>>>>>>
>>>>>> If this plan looks OK, I can send across patches doing this.
>>>>>>
>>>>>
>>>>> Looks good. I would also merge common.c with this resulting
>>>>> mach-exynos-dt.c, as it would be the only user of the code there.
>>>>
>>>>
>>>> Sounds good. While the naming is not important, I would just call the
>>>> file 'exynos.c', in line with some of the other platforms we have.
>>>> Both the 'mach-' and the '-dt' part of the file name are redundant.
>>>>
>>>> Alternatively, you could merge it all into common.c.
>>>
>>>
>>> exynos.c sounds good to me.
>>
Well, let me see common.c and mach-exynos.c, one is for SoC specific
stuff and the other is for Board specific so I think, keeping current
file would be good, we can change the file name mach-exynos.c or
board-exynos.c though.
Thanks,
Kukjin
>>
>> One minor thing. It might be a good idea to base on top of my PM
>> consolidation part 2 series, to avoid merge conflicts:
>>
>> http://thread.gmane.org/gmane.linux.ports.arm.kernel/299340
>>
>> It should hit Kgene's tree this weekend.
>
> Sure.
>
next prev parent reply other threads:[~2014-02-25 0:35 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 11:34 [PATCH 1/1] ARM: Exynos: Add generic compatible string Sachin Kamat
2014-02-19 12:45 ` Tomasz Figa
2014-02-19 12:45 ` Tomasz Figa
2014-02-20 4:14 ` Sachin Kamat
2014-02-20 4:14 ` Sachin Kamat
[not found] ` <CAK9yfHy7YHDLCfUGA-ua4iLzK2PMotVZvC=51t-bMkVZVBQFaA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-02-20 14:51 ` Tomasz Figa
2014-02-20 14:51 ` Tomasz Figa
2014-02-20 17:00 ` Arnd Bergmann
2014-02-20 17:00 ` Arnd Bergmann
[not found] ` <201402201800.49425.arnd-r2nGTMty4D4@public.gmane.org>
2014-02-20 17:34 ` Tomasz Figa
2014-02-20 17:34 ` Tomasz Figa
2014-02-20 17:48 ` Arnd Bergmann
2014-02-20 17:48 ` Arnd Bergmann
2014-02-21 6:08 ` Sachin Kamat
2014-02-21 6:08 ` Sachin Kamat
2014-02-21 13:18 ` Tomasz Figa
2014-02-21 13:18 ` Tomasz Figa
2014-02-21 14:48 ` Arnd Bergmann
2014-02-21 14:48 ` Arnd Bergmann
2014-02-21 15:21 ` Tomasz Figa
2014-02-21 15:21 ` Tomasz Figa
[not found] ` <53076F00.7000001-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-02-21 15:31 ` Tomasz Figa
2014-02-21 15:31 ` Tomasz Figa
2014-02-24 12:03 ` Sachin Kamat
2014-02-24 12:03 ` Sachin Kamat
2014-02-25 0:35 ` Kukjin Kim [this message]
2014-02-25 0:35 ` Kukjin Kim
2014-02-25 0:52 ` Tomasz Figa
2014-02-25 0:52 ` Tomasz Figa
2014-02-25 1:00 ` Kukjin Kim
2014-02-25 1:00 ` Kukjin Kim
2014-02-25 3:03 ` Sachin Kamat
2014-02-25 3:03 ` Sachin Kamat
2014-02-25 4:42 ` Olof Johansson
2014-02-25 4:42 ` Olof Johansson
2014-02-25 11:42 ` Arnd Bergmann
2014-02-25 11:42 ` Arnd Bergmann
2014-03-05 8:25 ` Sachin Kamat
2014-03-05 8:25 ` Sachin Kamat
2014-03-05 12:12 ` Tomasz Figa
2014-03-05 12:12 ` Tomasz Figa
2014-03-05 15:30 ` Sachin Kamat
2014-03-05 15:30 ` Sachin Kamat
2014-02-24 12:02 ` 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=530BE557.20106@samsung.com \
--to=kgene.kim@samsung.com \
--cc=Mark.Rutland@arm.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@secretlab.ca \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=sachin.kamat@linaro.org \
--cc=t.figa@samsung.com \
/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.