From: Kukjin Kim <kgene.kim@samsung.com>
To: 'Kukjin Kim' <kgene.kim@samsung.com>,
'Sylwester Nawrocki' <sylvester.nawrocki@gmail.com>,
'Shaik Ameer Basha' <shaik.samsung@gmail.com>
Cc: 'Olof Johansson' <olof@lixom.net>,
'Sylwester Nawrocki' <s.nawrocki@samsung.com>,
'Thomas Abraham' <thomas.abraham@linaro.org>,
'Shaik Ameer Basha' <shaik.ameer@samsung.com>,
linux-samsung-soc@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org, sy0816.kang@samsung.com,
olofj@google.com, thomas.ab@samsung.com, sachin.kamat@linaro.org,
joshi@samsung.com, sungchun.kang@samsung.com,
'Rob Herring' <rob.herring@calxeda.com>
Subject: RE: [PATCH v3 2/2] ARM: EXYNOS: Add Gscaler device from DT
Date: Sat, 11 Aug 2012 13:08:20 +0900 [thread overview]
Message-ID: <0efb01cd7776$f1b6fcc0$d524f640$%kim@samsung.com> (raw)
In-Reply-To:
Kukjin Kim wrote:
>
> Sylwester Nawrocki wrote:
> >
> > On 08/06/2012 08:27 AM, Shaik Ameer Basha wrote:
> > > After all this discussion, I can see two possibilities here.
> > > 1] If Kukjin Kim is sure about G-Scaler remains unchanged, across all
> > > the exynos5 series SoCs,
> > > It is fine to go with the compatible string
"samsung,exynos5-
> gsc".
> > > 2] Otherwise in case of any doubts about G-Scaler is going to change,
> > > It is safe to go with the compatible string specific to
> > > current SoC i.e., "samsung,exynos5250-gsc".
> > >
> > > If we all can agree on this, lets Kukjin Kim decide which string to
> > > use as he has good knowledge about upcoming exynos5 series SoCs.
> >
> > I don't have strong opinion on this, but my vote goes for using more
> > specific properties. Of course the final word belongs to Mr. Kim.
> >
> Thanks, and I will discuss with exynos hardware chip designers about that,
> then let you know.
>
'exynos5-gsc' should be ok on EXYNOS5250 and upcoming EXYNOS5 SoCs.
If any updates, I'll let you know.
Thanks.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
prev parent reply other threads:[~2012-08-11 4:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 13:08 [PATCH v3 0/2] Add device tree and clock support for Gscaler Shaik Ameer Basha
2012-07-20 13:08 ` [PATCH v3 1/2] ARM: EXYNOS: Add " Shaik Ameer Basha
2012-08-01 6:24 ` Kukjin Kim
2012-08-01 7:07 ` Shaik Ameer Basha
2012-07-20 13:08 ` [PATCH v3 2/2] ARM: EXYNOS: Add Gscaler device from DT Shaik Ameer Basha
2012-08-01 6:40 ` Kukjin Kim
2012-08-01 7:10 ` Shaik Ameer Basha
2012-08-01 7:48 ` Thomas Abraham
2012-08-01 8:15 ` Kukjin Kim
2012-08-01 8:18 ` Sylwester Nawrocki
2012-08-01 9:00 ` Kukjin Kim
2012-08-01 19:03 ` Sylwester Nawrocki
[not found] ` <50197D66.1050108-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-08-02 16:33 ` Olof Johansson
2012-08-02 23:40 ` Sylwester Nawrocki
2012-08-06 6:27 ` Shaik Ameer Basha
2012-08-06 19:09 ` Sylwester Nawrocki
2012-08-07 10:01 ` Kukjin Kim
2012-08-11 4:08 ` Kukjin Kim [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='0efb01cd7776$f1b6fcc0$d524f640$%kim@samsung.com' \
--to=kgene.kim@samsung.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=joshi@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=olofj@google.com \
--cc=rob.herring@calxeda.com \
--cc=s.nawrocki@samsung.com \
--cc=sachin.kamat@linaro.org \
--cc=shaik.ameer@samsung.com \
--cc=shaik.samsung@gmail.com \
--cc=sungchun.kang@samsung.com \
--cc=sy0816.kang@samsung.com \
--cc=sylvester.nawrocki@gmail.com \
--cc=thomas.ab@samsung.com \
--cc=thomas.abraham@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 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).