From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 5/8] clk: rockchip: add new clock type and controller for rk3036
Date: Thu, 01 Oct 2015 10:12:34 +0200 [thread overview]
Message-ID: <17410513.afcQr96dHz@diego> (raw)
In-Reply-To: <1443492833-15630-6-git-send-email-zhengxing@rock-chips.com>
Am Dienstag, 29. September 2015, 10:13:50 schrieb Xing Zheng:
> The rk3036's pll and clock are different with base on the rk3066(rk3188,
> rk3288, rk3368 use it), there are different adjust foctors and control
> registers, so these should be independent and separate from the series
> of rk3066s.
subject should probably be like
clk: rockchip: add new pll-type for rk3036 and similar socs
And the general handling should probably be implemented similar to the example
I posted in the v2 thread yesterday. [of course folded in and not as a
separate patch ;-) ]
Heiko
next prev parent reply other threads:[~2015-10-01 8:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 2:13 [PATCH v3 0/8] Build and support rk3036 SoC platform Xing Zheng
2015-09-29 2:13 ` [PATCH v3 1/8] ARM: dts: rockchip: add core rk3036 dts Xing Zheng
2015-10-04 16:54 ` kbuild test robot
2015-09-29 2:13 ` [PATCH v3 3/8] clk: rockchip: add clock controller for rk3036 Xing Zheng
2015-09-29 2:13 ` [PATCH v3 4/8] dt-bindings: add documentation of rk3036 clock controller Xing Zheng
2015-09-29 2:13 ` [PATCH v3 5/8] clk: rockchip: add new clock type and controller for rk3036 Xing Zheng
2015-10-01 8:12 ` Heiko Stübner [this message]
2015-10-01 8:46 ` zhengxing
2015-09-29 2:13 ` [PATCH v3 6/8] ARM: rockchip: add support smp " Xing Zheng
2015-10-02 9:19 ` Heiko Stübner
2015-09-29 2:37 ` [PATCH v3 7/8] ARM: dts: enable " Xing Zheng
2015-09-29 2:44 ` [PATCH v3 8/8] rockchip: make sure timer5 is enabled on rk3036 platforms 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=17410513.afcQr96dHz@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).