From: boris.brezillon@free-electrons.com (Boris BREZILLON)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] clk: at91: fix USB clk support on at91rm9200/sam9 SoCs
Date: Wed, 3 Sep 2014 10:08:28 +0200 [thread overview]
Message-ID: <20140903100828.69cc79fe@bbrezillon> (raw)
In-Reply-To: <20140902223846.5251.86384@quantum>
Hi Mike,
On Tue, 02 Sep 2014 15:38:46 -0700
Mike Turquette <mturquette@linaro.org> wrote:
> Quoting Boris BREZILLON (2014-09-02 00:50:13)
> > Hi,
> >
> > This patch series fixes several bugs in the PLL driver preventing a proper
> > set_rate on the PLL clk.
> > It also enables propagation of set_rate request on the USB clk in order to
> > configure the PLL rate according to the USB block requirement (48 MHz).
> >
> > Note that existing kernels, relying on the PLL configuration made by the
> > the bootloader should not be impacted by this bug, but others (those
> > directly booting from at91bootstrap or not enabling USB support in the
> > bootloader) will be.
> >
> > This bug was reported by Ga?l, who's directly booting the kernel from the
> > bootstrap.
>
> Applied to clk-next.
Thanks for applying this series to clk-next, but I wonder if we
shouldn't try to get this merged in 3.17 (in order to avoid back-porting
these fixes to 3.17 stable branch).
I know I said it shouldn't impact that much users, but IMHO we
shouldn't rely on this assumption.
Let me know if you're okay to take these patches in clk-fixes, because
this patch [1] needs to be applied first (I guess Nicolas will take it
through his -fixes branch).
Best Regards,
Boris
[1]https://lkml.org/lkml/2014/9/1/634
>
> Regards,
> Mike
>
> >
> > Best Regards,
> >
> > Boris
> >
> > Boris BREZILLON (5):
> > clk: at91: fix PLL_MAX_COUNT macro definition
> > clk: at91: rework PLL rate calculation
> > clk: at91: fix recalc_rate implementation of PLL driver
> > clk: at91: rework rm9200 USB clock to propagate set_rate to the parent
> > clk
> > clk: at91: fix div by zero in USB clock driver
> >
> > drivers/clk/at91/clk-pll.c | 160 +++++++++++++++++++++++----------------------
> > drivers/clk/at91/clk-usb.c | 20 ++++--
> > 2 files changed, 96 insertions(+), 84 deletions(-)
> >
> > --
> > 1.9.1
> >
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-09-03 8:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 7:50 [PATCH 0/5] clk: at91: fix USB clk support on at91rm9200/sam9 SoCs Boris BREZILLON
2014-09-02 7:50 ` [PATCH 1/5] clk: at91: fix PLL_MAX_COUNT macro definition Boris BREZILLON
2014-09-02 7:50 ` [PATCH 2/5] clk: at91: rework PLL rate calculation Boris BREZILLON
2014-09-02 7:50 ` [PATCH 3/5] clk: at91: fix recalc_rate implementation of PLL driver Boris BREZILLON
2014-09-02 7:50 ` [PATCH 4/5] clk: at91: rework rm9200 USB clock to propagate set_rate to the parent clk Boris BREZILLON
2014-09-02 7:50 ` [PATCH 5/5] clk: at91: fix div by zero in USB clock driver Boris BREZILLON
2014-09-02 22:38 ` [PATCH 0/5] clk: at91: fix USB clk support on at91rm9200/sam9 SoCs Mike Turquette
2014-09-03 8:08 ` Boris BREZILLON [this message]
[not found] ` <20140903172005.11368.11852@quantum>
2014-09-03 17:43 ` Boris BREZILLON
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=20140903100828.69cc79fe@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--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).