linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH v2 1/5] clk: rockchip: add more mux parameters for new pll sources
Date: Wed, 09 Mar 2016 02:12:31 +0100	[thread overview]
Message-ID: <2242962.kh0Ty0L2C4@phil> (raw)
In-Reply-To: <1456827275-8035-2-git-send-email-zhengxing@rock-chips.com>

Am Dienstag, 1. M?rz 2016, 18:14:31 schrieb Xing Zheng:
> Thers are only two parent PLLs that APLL and GPLL for core on the
> previous SoCs (RK3066/RK3188/RK3288/RK3368). Hence, we set fixed
> GPLL as alternate parent when core is switching freq.
> 
> Since RK3399 big.LITTLE architecture, we need to select and adapt
> more PLLs (ALPLL/ABPLL/DPLL/GPLL) sources.
> 
> Signed-off-by: Xing Zheng <zhengxing@rock-chips.com>

note to self: looks good to go

  reply	other threads:[~2016-03-09  1:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-01 10:14 [RESEND PATCH v2 0/5] Add more clock compatible features and support the RK3399 clock Xing Zheng
2016-03-01 10:14 ` [RESEND PATCH v2 1/5] clk: rockchip: add more mux parameters for new pll sources Xing Zheng
2016-03-09  1:12   ` Heiko Stuebner [this message]
2016-03-01 10:14 ` [RESEND PATCH v2 2/5] clk: rockchip: Add support for multiple clock providers Xing Zheng
2016-03-01 10:14 ` [RESEND PATCH v2 3/5] clk: rockchip: add new pll-type for rk3399 and similar socs Xing Zheng
2016-03-09  1:22   ` Heiko Stuebner
2016-03-09  2:20     ` Xing Zheng
2016-03-01 10:14 ` [RESEND PATCH v2 4/5] clk: rockchip: add a COMPOSITE_FRACMUX_NOGATE type Xing Zheng
2016-03-01 10:15 ` [RESEND PATCH v2 5/5] clk: rockchip: add clock controller for the RK3399 Xing Zheng
2016-03-08 23:34   ` Doug Anderson
2016-03-09  0:51     ` Jianqun Xu
2016-03-09  1:26       ` Xing Zheng

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=2242962.kh0Ty0L2C4@phil \
    --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).