From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: jg1.han@samsung.com
Cc: Sylwester Nawrocki <snjw23@gmail.com>,
Kukjin Kim <kgene.kim@samsung.com>,
Paul Mundt <lethal@linux-sh.org>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
Jong-Hun Han <jonghun.han@samsung.com>,
ANAND KUMAR N <anand.kn@samsung.com>,
THOMAS P ABRAHAM <thomas.ab@samsung.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Kyungmin Park <kmpark@infradead.org>,
In-Ki Dae <inki.dae@samsung.com>,
ARM Linux <linux@arm.linux.org.uk>,
Ben Dooks <ben-linux@fluff.org>
Subject: Re: [PATCH v2 1/5] ARM: EXYNOS4: Change clock name for FIMD
Date: Tue, 21 Jun 2011 10:21:58 +0200 [thread overview]
Message-ID: <4E0054A6.9080401@samsung.com> (raw)
In-Reply-To: <22737339.68511308629879847.JavaMail.weblogic@epml09>
On 06/21/2011 06:18 AM, JinGoo Han wrote:
>>> ----------+-----------------------+------------------------+
>>> exynos4 | ACLK_160 (fimd) | O | SCLK_FIMD (sclk_fimd)|
>>> ----------+------------------------+-----------------------+
>> ^^^^^^^^^^^^^^^^^^^
>> In mach-exynos4/clock.c this clock is described as ACLK_133 (lcd)
> I cannot find it.
> Let me know where 'fimd' is described as ACLK_133.
> Anyway, according to datasheet, this clock is described as ACLK_160.
My apologies, I had been looking not at the mainline source, just some
internal tree. And that's right it is described as ACLK_160 in the datasheet.
next prev parent reply other threads:[~2011-06-21 8:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 4:18 Re: [PATCH v2 1/5] ARM: EXYNOS4: Change clock name for FIMD JinGoo Han
2011-06-21 8:21 ` Sylwester Nawrocki [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-20 7:14 JinGoo Han
2011-06-20 9:47 ` Sylwester Nawrocki
2011-06-20 10:09 ` daeinki
2011-06-20 20:33 ` Sylwester Nawrocki
2011-06-21 0:20 ` daeinki
2011-06-20 21:51 ` Sylwester Nawrocki
2011-06-17 13:01 Jingoo Han
2011-06-19 21:39 ` Sylwester Nawrocki
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=4E0054A6.9080401@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=anand.kn@samsung.com \
--cc=ben-linux@fluff.org \
--cc=inki.dae@samsung.com \
--cc=jg1.han@samsung.com \
--cc=jonghun.han@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=kmpark@infradead.org \
--cc=lethal@linux-sh.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=m.szyprowski@samsung.com \
--cc=snjw23@gmail.com \
--cc=thomas.ab@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.