From: Dongjin Kim <Dongjin.Kim@agreeyamobility.net>
To: Olof Johansson <olof@lixom.net>
Cc: "Thomas Abraham" <thomas.abraham@linaro.org>,
"Dongjin Kim" <tobetter@gmail.com>,
"Kukjin Kim" <kgene.kim@samsung.com>,
"Russell King" <linux@arm.linux.org.uk>,
"Tony Lindgren" <tony@atomide.com>,
"Jon Medhurst" <tixy@yxit.co.uk>,
"Shawn Guo" <shawn.guo@linaro.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: 회신: 회신: [PATCH] ODROID-X: hkdk4412: Add new hardware based on Exynos4412
Date: Tue, 7 Aug 2012 02:05:56 +0000 [thread overview]
Message-ID: <A6A3B7488C419F488E5B13FFD03C08AD2F43688D@SN2PRD0510MB370.namprd05.prod.outlook.com> (raw)
In-Reply-To: <CAOesGMh=6QrCmL4EqnSqTxi1nH+8Wn+x=z9BYq8QJCznH3a=zQ@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1939 bytes --]
Hello,
I am trying to understand what I have to do for device tree.
In order to create dts file for ODROID-X hardware, it seems I may need dts file of EXYNOS4412 SoC.
But maybe exynos4412.dtsi is not merged yet or not exist, like exynos4210.dtsi or exynos5250.dtsi.
Obviously it seems not easy to create such a file without SoC datasheet, and I do not have it.
So do I wait for the file to be merged by Samsung or better to create initial dts file cloned from exynos4210.dtsi and modify to have verified nodes with the source/header files?
What's your suggestion?
Regards,
Dongjin.
________________________________________
ë³´ë¸ ì¬ë: Olof Johansson [olof@lixom.net]
ë³´ë¸ ë ì§: 2012ë
8ì 7ì¼ íìì¼ ì¤ì 3:33
ë°ë ì¬ë: Dongjin Kim
참조: Thomas Abraham; Dongjin Kim; Kukjin Kim; Russell King; Tony Lindgren; Jon Medhurst; Shawn Guo; Uwe Kleine-König; linux-arm-kernel@lists.infradead.org; linux-samsung-soc@vger.kernel.org; linux-kernel@vger.kernel.org
ì 목: Re: íì : [PATCH] ODROID-X: hkdk4412: Add new hardware based on Exynos4412
Hi,
On Mon, Aug 6, 2012 at 11:16 AM, Dongjin Kim
<Dongjin.Kim@agreeyamobility.net> wrote:
> Hello Tomas,
>
> I am agree with you to look at using device tree and I have some plan for it.
> But as of now I am focusing to bring up the hardware itself with mainline kernel and merge into it.
> I also need some time to look at the requirement of device tree, because I am not familiar with it yet.
>
> Any advice will be welcomed.
Basic rule (that has some flexibility for legacy platforms) is that
the net movement of board support should move from board files to
device-tree based. Introduction of a brand new board like this is a
prime example of something that should be using device tree from day
1.
-Olof
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
WARNING: multiple messages have this Message-ID (diff)
From: Dongjin Kim <Dongjin.Kim@agreeyamobility.net>
To: Olof Johansson <olof@lixom.net>
Cc: "Thomas Abraham" <thomas.abraham@linaro.org>,
"Dongjin Kim" <tobetter@gmail.com>,
"Kukjin Kim" <kgene.kim@samsung.com>,
"Russell King" <linux@arm.linux.org.uk>,
"Tony Lindgren" <tony@atomide.com>,
"Jon Medhurst" <tixy@yxit.co.uk>,
"Shawn Guo" <shawn.guo@linaro.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: 회신: 회신: [PATCH] ODROID-X: hkdk4412: Add new hardware based on Exynos4412
Date: Tue, 7 Aug 2012 02:05:56 +0000 [thread overview]
Message-ID: <A6A3B7488C419F488E5B13FFD03C08AD2F43688D@SN2PRD0510MB370.namprd05.prod.outlook.com> (raw)
In-Reply-To: <CAOesGMh=6QrCmL4EqnSqTxi1nH+8Wn+x=z9BYq8QJCznH3a=zQ@mail.gmail.com>
Hello,
I am trying to understand what I have to do for device tree.
In order to create dts file for ODROID-X hardware, it seems I may need dts file of EXYNOS4412 SoC.
But maybe exynos4412.dtsi is not merged yet or not exist, like exynos4210.dtsi or exynos5250.dtsi.
Obviously it seems not easy to create such a file without SoC datasheet, and I do not have it.
So do I wait for the file to be merged by Samsung or better to create initial dts file cloned from exynos4210.dtsi and modify to have verified nodes with the source/header files?
What's your suggestion?
Regards,
Dongjin.
________________________________________
보낸 사람: Olof Johansson [olof@lixom.net]
보낸 날짜: 2012년 8월 7일 화요일 오전 3:33
받는 사람: Dongjin Kim
참조: Thomas Abraham; Dongjin Kim; Kukjin Kim; Russell King; Tony Lindgren; Jon Medhurst; Shawn Guo; Uwe Kleine-König; linux-arm-kernel@lists.infradead.org; linux-samsung-soc@vger.kernel.org; linux-kernel@vger.kernel.org
제목: Re: 회신: [PATCH] ODROID-X: hkdk4412: Add new hardware based on Exynos4412
Hi,
On Mon, Aug 6, 2012 at 11:16 AM, Dongjin Kim
<Dongjin.Kim@agreeyamobility.net> wrote:
> Hello Tomas,
>
> I am agree with you to look at using device tree and I have some plan for it.
> But as of now I am focusing to bring up the hardware itself with mainline kernel and merge into it.
> I also need some time to look at the requirement of device tree, because I am not familiar with it yet.
>
> Any advice will be welcomed.
Basic rule (that has some flexibility for legacy platforms) is that
the net movement of board support should move from board files to
device-tree based. Introduction of a brand new board like this is a
prime example of something that should be using device tree from day
1.
-Olof
WARNING: multiple messages have this Message-ID (diff)
From: Dongjin.Kim@agreeyamobility.net (Dongjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: 회신: 회신: [PATCH] ODROID-X: hkdk4412: Add new hardware based on Exynos4412
Date: Tue, 7 Aug 2012 02:05:56 +0000 [thread overview]
Message-ID: <A6A3B7488C419F488E5B13FFD03C08AD2F43688D@SN2PRD0510MB370.namprd05.prod.outlook.com> (raw)
In-Reply-To: <CAOesGMh=6QrCmL4EqnSqTxi1nH+8Wn+x=z9BYq8QJCznH3a=zQ@mail.gmail.com>
Hello,
I am trying to understand what I have to do for device tree.
In order to create dts file for ODROID-X hardware, it seems I may need dts file of EXYNOS4412 SoC.
But maybe exynos4412.dtsi is not merged yet or not exist, like exynos4210.dtsi or exynos5250.dtsi.
Obviously it seems not easy to create such a file without SoC datasheet, and I do not have it.
So do I wait for the file to be merged by Samsung or better to create initial dts file cloned from exynos4210.dtsi and modify to have verified nodes with the source/header files?
What's your suggestion?
Regards,
Dongjin.
________________________________________
?? ??: Olof Johansson [olof at lixom.net]
?? ??: 2012? 8? 7? ??? ?? 3:33
?? ??: Dongjin Kim
??: Thomas Abraham; Dongjin Kim; Kukjin Kim; Russell King; Tony Lindgren; Jon Medhurst; Shawn Guo; Uwe Kleine-K?nig; linux-arm-kernel at lists.infradead.org; linux-samsung-soc at vger.kernel.org; linux-kernel at vger.kernel.org
??: Re: ??: [PATCH] ODROID-X: hkdk4412: Add new hardware based on Exynos4412
Hi,
On Mon, Aug 6, 2012 at 11:16 AM, Dongjin Kim
<Dongjin.Kim@agreeyamobility.net> wrote:
> Hello Tomas,
>
> I am agree with you to look at using device tree and I have some plan for it.
> But as of now I am focusing to bring up the hardware itself with mainline kernel and merge into it.
> I also need some time to look at the requirement of device tree, because I am not familiar with it yet.
>
> Any advice will be welcomed.
Basic rule (that has some flexibility for legacy platforms) is that
the net movement of board support should move from board files to
device-tree based. Introduction of a brand new board like this is a
prime example of something that should be using device tree from day
1.
-Olof
next prev parent reply other threads:[~2012-08-07 2:06 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-06 14:10 [PATCH] ODROID-X: hkdk4412: Add new hardware based on Exynos4412 Dongjin Kim
2012-08-06 14:10 ` Dongjin Kim
2012-08-06 14:10 ` Dongjin Kim
2012-08-06 14:57 ` Mark Brown
2012-08-06 14:57 ` Mark Brown
2012-08-06 17:37 ` Thomas Abraham
2012-08-06 17:37 ` Thomas Abraham
2012-08-06 18:16 ` 회신: " Dongjin Kim
2012-08-06 18:16 ` Dongjin Kim
2012-08-06 18:16 ` Dongjin Kim
2012-08-06 18:33 ` Olof Johansson
2012-08-06 18:33 ` Olof Johansson
2012-08-07 2:05 ` Dongjin Kim [this message]
2012-08-07 2:05 ` 회신: " Dongjin Kim
2012-08-07 2:05 ` Dongjin Kim
2012-08-07 2:28 ` Olof Johansson
2012-08-07 2:56 ` 회신: " Dongjin Kim
2012-08-07 2:56 ` Dongjin Kim
2012-08-07 2:56 ` Dongjin Kim
2012-08-07 4:14 ` Thomas Abraham
2012-08-07 4:38 ` Kyungmin Park
2012-08-07 18:49 ` [PATCH v2] " Dongjin Kim
2012-08-07 18:49 ` Dongjin Kim
2012-08-07 18:49 ` Dongjin Kim
2012-08-08 2:23 ` Kukjin Kim
2012-08-08 2:23 ` Kukjin Kim
2012-08-08 2:41 ` 회신: " Dongjin Kim
2012-08-08 2:41 ` Dongjin Kim
2012-08-08 2:41 ` Dongjin Kim
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=A6A3B7488C419F488E5B13FFD03C08AD2F43688D@SN2PRD0510MB370.namprd05.prod.outlook.com \
--to=dongjin.kim@agreeyamobility.net \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=olof@lixom.net \
--cc=shawn.guo@linaro.org \
--cc=thomas.abraham@linaro.org \
--cc=tixy@yxit.co.uk \
--cc=tobetter@gmail.com \
--cc=tony@atomide.com \
--cc=u.kleine-koenig@pengutronix.de \
/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.