From: Tomasz Figa <t.figa@samsung.com>
To: Arun Kumar K <arunkk.samsung@gmail.com>
Cc: Doug Anderson <dianders@chromium.org>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
Mike Turquette <mturquette@linaro.org>,
Kukjin Kim <kgene.kim@samsung.com>,
Yadwinder Singh Brar <yadi.brar@samsung.com>
Subject: Re: [PATCH] clk: samsung: Fix PLL35XX lock time
Date: Thu, 10 Oct 2013 07:20:31 +0200 [thread overview]
Message-ID: <2947491.pJZ8F0UW5m@amdn883> (raw)
In-Reply-To: <CALt3h78Lt2epHFmKeQ90839-L4XSQL+rDUTHGj681S2sTG=Jeg@mail.gmail.com>
Hi Arun,
On Wednesday 09 of October 2013 09:21:43 Arun Kumar K wrote:
> Hi Doug,
>
> On Tue, Oct 8, 2013 at 9:39 PM, Doug Anderson <dianders@chromium.org> wrote:
> > Arun,
> >
> > On Mon, Oct 7, 2013 at 11:56 PM, Arun Kumar K <arun.kk@samsung.com> wrote:
> >> PLL35XX lock factor is 250 as per the manual whereas its
> >> wrongly set as 270 now.
> >>
> >> Signed-off-by: Arun Kumar K <arun.kk@samsung.com>
> >> ---
> >>
> >> drivers/clk/samsung/clk-pll.c | 4 ++--
> >> 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > I don't think this is right. I believe that it needs to be passed in
> > by the SoC. On exynos5250 I see 250 in both the manual and in our
> > code. On exynos5420 manual I actually see 200 now. I'm not actually
> > sure where the 270 came from, now that I search for it.
>
> The manual I referred gives 250 for both 5250 and 5420 and thats why I
> concluded on this fix. I will check other versions of the manual to see if
> the value is changing.
270 is the value taken from Exynos 4412 User's Manual rev. 1.1.
I believe we don't have to extend this to support per SoC value, because it
should be always safe to take the value of SoC that requires the longest
locking period. The differences are small enough to be insignificant, so there
should be no practical performance penalty.
Best regards,
Tomasz
next prev parent reply other threads:[~2013-10-10 5:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 6:56 [PATCH] clk: samsung: Fix PLL35XX lock time Arun Kumar K
2013-10-08 16:09 ` Doug Anderson
2013-10-09 3:51 ` Arun Kumar K
2013-10-10 5:20 ` Tomasz Figa [this message]
2013-10-11 15:14 ` Doug Anderson
2013-10-12 2:06 ` Tomasz Figa
2013-10-15 4:08 ` Doug Anderson
2013-10-15 16:46 ` Sonny Rao
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=2947491.pJZ8F0UW5m@amdn883 \
--to=t.figa@samsung.com \
--cc=arunkk.samsung@gmail.com \
--cc=dianders@chromium.org \
--cc=kgene.kim@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=yadi.brar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox