From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: rockchip: Fix PLL bandwidth
Date: Wed, 22 Jul 2015 00:14:19 +0200 [thread overview]
Message-ID: <3846129.lKetE2zB83@diego> (raw)
In-Reply-To: <55AEB6AE.2070006@codeaurora.org>
Am Dienstag, 21. Juli 2015, 14:16:30 schrieb Stephen Boyd:
> On 07/21/2015 01:41 PM, Douglas Anderson wrote:
> > In the TRM we see that BWADJ is "a 12-bit bus that selects the values
> >
> > 1-4096 for the bandwidth divider (NB)":
> > NB = BWADJ[11:0] + 1
> >
> > The recommended setting of NB: NB = NF / 2.
> >
> > So:
> > NB = NF / 2
> > BWADJ[11:0] + 1 = NF / 2
> > BWADJ[11:0] = NF / 2 - 1
> >
> > Right now, we have:
> >
> > { \
> >
> > .rate = _rate##U, \
> > .nr = _nr, \
> > .nf = _nf, \
> > .no = _no, \
> > .bwadj = (_nf >> 1), \
> >
> > }
> >
> > That means we set bwadj to NF / 2, not NF / 2 - 1
> >
> > All of this is a bit confusing because we specify "NR" (the 1-based
> > value), "NF" (the 1-based value), "NO" (the 1-based value), but
> > "BWADJ" (the 0-based value) instead of "NB" (the 1-based value).
> >
> > Let's change to working with "NB" and fix the off by one error. This
> > may affect PLL jitter in a small way (hopefully for the better).
> >
> > Signed-off-by: Douglas Anderson <dianders@chromium.org>
>
> There's no Fixes tag or stable Cc so I take it this isn't fixing any
> manifesting regression, more of a visual inspection bug find?
Looks like it ... i.e. all Rockchip SoCs I have (rk3066, rk3188, rk3288,
rk3368) run fine for me with the off-by-one setting till now.
next prev parent reply other threads:[~2015-07-21 22:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 20:41 [PATCH] clk: rockchip: Fix PLL bandwidth Douglas Anderson
2015-07-21 21:04 ` Heiko Stübner
2015-07-21 21:16 ` Stephen Boyd
2015-07-21 22:14 ` Heiko Stübner [this message]
2015-07-21 22:37 ` Doug Anderson
2015-07-21 22:43 ` Stephen Boyd
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=3846129.lKetE2zB83@diego \
--to=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.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).