From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/4] clk: rockchip: allow adjusting pll rates on init
Date: Tue, 25 Nov 2014 12:28:10 +0100 [thread overview]
Message-ID: <1753789.atZ8FgoESr@diego> (raw)
In-Reply-To: <1416512333-15438-1-git-send-email-heiko@sntech.de>
Am Donnerstag, 20. November 2014, 20:38:49 schrieb Heiko Stuebner:
> It was found that some firmware versions initialized the pll rates using
> suboptimal parameters to achieve frequencies the actual rate table contained
> better parameters for.
>
> Therefore this series first adds the possibility to create pll-specific
> flags and then adds a flag to adjust the pll rate on init to the parameters
> from the rate table.
>
> changes since v1:
> - move population of pll_mux before registering the core pll clock
> null pointer exception in the _set_rate callback when called from init
>
> Heiko Stuebner (4):
> clk: rockchip: add ability to specify pll-specific flags
> clk: rockchip: setup pll_mux data earlier
> clk: rockchip: add optional sync to pll rate parameters
> clk: rockchip: add ROCKCHIP_PLL_SYNC_RATE flag to some plls
with Mike's green-light, I've now added these to my clk branch with Kevers
tags added.
prev parent reply other threads:[~2014-11-25 11:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 19:38 [PATCH v2 0/4] clk: rockchip: allow adjusting pll rates on init Heiko Stuebner
2014-11-20 19:38 ` [PATCH v2 1/4] clk: rockchip: add ability to specify pll-specific flags Heiko Stuebner
2014-11-20 19:38 ` [PATCH v2 2/4] clk: rockchip: setup pll_mux data earlier Heiko Stuebner
2014-11-20 19:38 ` [PATCH v2 3/4] clk: rockchip: add optional sync to pll rate parameters Heiko Stuebner
2014-11-20 19:38 ` [PATCH v2 4/4] clk: rockchip: add ROCKCHIP_PLL_SYNC_RATE flag to some plls Heiko Stuebner
2014-11-21 2:56 ` [PATCH v2 0/4] clk: rockchip: allow adjusting pll rates on init Kever Yang
2014-11-25 6:11 ` Mike Turquette
2014-11-25 11:28 ` Heiko Stübner [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=1753789.atZ8FgoESr@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 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.