From: Heiko Stuebner <heiko@sntech.de>
To: Andy Yan <andy.yan@rock-chips.com>
Cc: robh+dt@kernel.org, shawn.lin@rock-chips.com,
zhangqing@rock-chips.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, mturquette@baylibre.com,
sboyd@codeaurora.org, linux-rockchip@lists.infradead.org,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 04/23] clk: rockchip: support more rates for cpuclk
Date: Tue, 08 Aug 2017 00:52:13 +0200 [thread overview]
Message-ID: <3401435.hitepWLYJ1@phil> (raw)
In-Reply-To: <1501662743-11920-1-git-send-email-andy.yan@rock-chips.com>
Am Mittwoch, 2. August 2017, 16:32:23 CEST schrieb Andy Yan:
> From: Elaine Zhang <zhangqing@rock-chips.com>
>
> fix up the cpuclk rates table for support more freqs.
> fix up the mux_core_mask describe error.
>
> Signed-off-by: Elaine Zhang <zhangqing@rock-chips.com>
> Signed-off-by: Andy Yan <andy.yan@rock-chips.com>
applied for 4.14
Thanks
Heiko
next prev parent reply other threads:[~2017-08-07 22:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 8:25 [PATCH v2 00/23] Support more devices on rockchip rv1108 Andy Yan
2017-08-02 8:32 ` [PATCH v2 04/23] clk: rockchip: support more rates for cpuclk Andy Yan
2017-08-07 22:52 ` Heiko Stuebner [this message]
2017-08-02 8:33 ` [PATCH v2 05/23] clk: rockchip: fix up the pll clks error for rv1108 SoC Andy Yan
2017-08-07 22:52 ` Heiko Stuebner
2017-08-02 8:33 ` [PATCH v2 06/23] clk: rockchip: support more clks for rv1108 Andy Yan
2017-08-07 22:57 ` Heiko Stuebner
2017-08-02 8:34 ` [PATCH v2 07/23] clk: rockchip: fix up some clks describe error for rv1108 SoC Andy Yan
2017-08-02 8:35 ` [PATCH v2 08/23] clk: rockchip: rename some of clks " Andy Yan
2017-08-02 8:36 ` [PATCH v2 09/23] clk: rockchip: add some critical clocks " Andy Yan
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=3401435.hitepWLYJ1@phil \
--to=heiko@sntech.de \
--cc=andy.yan@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=shawn.lin@rock-chips.com \
--cc=zhangqing@rock-chips.com \
/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).