From: Leo Yan <leo.yan@linaro.org>
To: Wei Xu <xuwei5@hisilicon.com>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Zhangfei Gao <zhangfei.gao@linaro.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
Guodong Xu <guodong.xu@linaro.org>,
Haojian Zhuang <haojian.zhuang@linaro.org>
Cc: Leo Yan <leo.yan@linaro.org>
Subject: [PATCH v3 0/2] Hi3660: enable sp804 timer
Date: Mon, 22 May 2017 12:52:26 +0800 [thread overview]
Message-ID: <1495428748-11153-1-git-send-email-leo.yan@linaro.org> (raw)
This patch set is to enable sp804 timer on Hi3660 for Hikey960 platform.
On Hi3660, the sp804 timer co-exists with CPUs' architecture timer; but
sp804 timer is located in SoC level but CPU's architecture timer is in
CPU power domain. sp804 timer is used as broadcast timer when CPU enters
idle states and the CPU (includes architecture timer) power domain is
powered off. So sp804 timer enabling is prerequisite before we enable
CPUIdle on Hi3660.
This patch set is to enable sp804 timer, the first patch is to adjust
subset of crgctrl clock regiseration to CLK_OF_DECLARE_DRIVER method
so ensure timer clock is avaiable when timer probing. The second patch
is to add description for timer in dts. Have rebased this patch set on
Guodong's dts patch set [1] and verified this patch set on Hikey960.
[1] http://archive.armlinux.org.uk/lurker/message/20170517.083733.8207a50e.en.html
Changes from v2:
* According to Stephen's suggestion, only changed necessary clocks
of fixed_rate_clks to CLK_OF_DECLARE_DRIVER method.
Changes from v1:
* Follow Steven's suggestion on IRC, Change to only use
CLK_OF_DECLARE_DRIVER for crgctrl clock.
Leo Yan (2):
clk: Hi3660: register fixed_rate_clks with CLK_OF_DECLARE_DRIVER
arm64: dts: add sp804 timer node for Hi3660
arch/arm64/boot/dts/hisilicon/hi3660.dtsi | 11 +++++++
drivers/clk/hisilicon/clk-hi3660.c | 48 ++++++++++++++++++++++++-------
2 files changed, 49 insertions(+), 10 deletions(-)
--
1.9.1
next reply other threads:[~2017-05-22 4:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 4:52 Leo Yan [this message]
2017-05-22 4:52 ` [PATCH v3 1/2] clk: Hi3660: register fixed_rate_clks with CLK_OF_DECLARE_DRIVER Leo Yan
2017-06-19 23:36 ` Stephen Boyd
[not found] ` <20170619233655.GR20170-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-06-20 0:09 ` Leo Yan
2017-05-22 4:52 ` [PATCH v3 2/2] arm64: dts: add sp804 timer node for Hi3660 Leo Yan
2017-06-15 20:00 ` Wei Xu
[not found] ` <5942E77A.8080500-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>
2017-06-15 23:59 ` Leo 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=1495428748-11153-1-git-send-email-leo.yan@linaro.org \
--to=leo.yan@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=guodong.xu@linaro.org \
--cc=haojian.zhuang@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=will.deacon@arm.com \
--cc=xuwei5@hisilicon.com \
--cc=zhangfei.gao@linaro.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).