From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] clk: sunxi: fix sun6i PLL1 .recalc_rate() result
Date: Wed, 28 Jan 2015 18:31:03 -0800 [thread overview]
Message-ID: <20150129023103.22722.42964@quantum> (raw)
In-Reply-To: <CAGb2v66JHK9adf5gUKdiByke4OdtGN2KFKC1srx7q_4tARJU_g@mail.gmail.com>
Quoting Chen-Yu Tsai (2015-01-28 13:57:14)
> On Wed, Jan 28, 2015 at 7:01 PM, Mike Turquette <mturquette@linaro.org> wrote:
> > Quoting Chen-Yu Tsai (2015-01-27 22:19:22)
> >> On Wed, Jan 28, 2015 at 2:41 AM, Mike Turquette <mturquette@linaro.org> wrote:
> >> > Quoting Maxime Ripard (2015-01-24 07:29:44)
> >> >> Hi Mike,
> >> >>
> >> >> On Sat, Jan 24, 2015 at 04:42:39PM +0800, Chen-Yu Tsai wrote:
> >> >> > PLL1 on sun6i has its N factor start from 1 (N = register value + 1).
> >> >> > Make the factors clk driver aware of this so clk_factors_recalc_rate()
> >> >> > gives the correct result.
> >> >> >
> >> >> > Cc: <stable@vger.kernel.org> # 3.12 9a5e6c7eb5cc clk: sunxi: Support factor
> >> >> > Cc: <stable@vger.kernel.org> # 3.12
> >> >> > Signed-off-by: Chen-Yu Tsai <wens@csie.org>
> >> >>
> >> >> Could you queue this for 3.19?
> >> >
> >> > This is fixed in 76820fc in clk-next, destined for 3.20.
> >> >
> >> > Also I'm confused by the stable tags above. Looks like 9a5e6c7eb5cc was
> >> > merged for 3.16, not 3.12.
> >>
> >> I think so. I wasn't quite sure what the version number was
> >> supposed to be, the first version it is applicable? or the
> >> first version the specific patch was merged.
> >
> > Chen-Yu,
> >
> > I think that struct clk_factors_config did not have the n_start member
> > before 9a5e6c7eb5cc, so this patch could not apply without 9a5e6c7eb5cc.
> > That's from memory though, and I might be mis-remembering.
>
> AFAIK the stable-commit doc explains the format above as cherry-picking
> 9a5e6c7eb5cc first, then applying this patch.
I just learned something new. I didn't know about the cherry-picking
format. That's cool.
>
> > The fix is not for a new regression, thus it is going into 3.20 and I am
> > remiss to rebase my tree to add a stable tag. Can you submit this to
> > stable yourself after 3.20-rc1? I think the proper thing to do is to
> > reference this patch and the commitlog to show that it was fixed
> > upstream.
>
> Sure. Also CC-ing Hans, as his name is on the patch for 3.20. :)
Thanks!
Regards,
Mike
>
> ChenYu
>
> > Regards,
> > Mike
> >
> >>
> >> ChenYu
> >>
> >> >>
> >> >> Thanks,
> >> >> Maxime
> >> >>
> >> >> --
> >> >> Maxime Ripard, Free Electrons
> >> >> Embedded Linux, Kernel and Android engineering
> >> >> http://free-electrons.com
prev parent reply other threads:[~2015-01-29 2:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-24 8:42 [PATCH v2] clk: sunxi: fix sun6i PLL1 .recalc_rate() result Chen-Yu Tsai
2015-01-24 15:29 ` Maxime Ripard
2015-01-28 1:41 ` Mike Turquette
2015-01-28 6:19 ` Chen-Yu Tsai
2015-01-28 18:01 ` Mike Turquette
2015-01-28 21:57 ` Chen-Yu Tsai
2015-01-29 2:31 ` Mike Turquette [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=20150129023103.22722.42964@quantum \
--to=mturquette@linaro.org \
--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