From: Stephen Boyd <sboyd@codeaurora.org>
To: Leo Yan <leo.yan@linaro.org>
Cc: Wei Xu <xuwei5@hisilicon.com>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Michael Turquette <mturquette@baylibre.com>,
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,
Dmitry Shmidt <dimitrysh@google.com>,
Guodong Xu <guodong.xu@linaro.org>,
Haojian Zhuang <haojian.zhuang@linaro.org>
Subject: Re: [PATCH 1/2] clk: hi6220: change watchdog clock source
Date: Thu, 31 Aug 2017 18:32:40 -0700 [thread overview]
Message-ID: <20170901013240.GM21656@codeaurora.org> (raw)
In-Reply-To: <1503993518-24428-1-git-send-email-leo.yan@linaro.org>
On 08/29, Leo Yan wrote:
> The old code uses tcxo (19.2MHz) as watchdog clock but actually the
> watchdog uses 32K clock, as result the watchdog timeout cannot be set
> correctly and delay long time to reset SoC.
>
> So this patch is to use 'ref32k' as clock source for watchdog.
>
> Fixes: 72ea48610d43 ("clk: hi6220: Clock driver support for Hisilicon hi6220 SoC")
> Signed-off-by: Leo Yan <leo.yan@linaro.org>
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] clk: hi6220: change watchdog clock source
Date: Thu, 31 Aug 2017 18:32:40 -0700 [thread overview]
Message-ID: <20170901013240.GM21656@codeaurora.org> (raw)
In-Reply-To: <1503993518-24428-1-git-send-email-leo.yan@linaro.org>
On 08/29, Leo Yan wrote:
> The old code uses tcxo (19.2MHz) as watchdog clock but actually the
> watchdog uses 32K clock, as result the watchdog timeout cannot be set
> correctly and delay long time to reset SoC.
>
> So this patch is to use 'ref32k' as clock source for watchdog.
>
> Fixes: 72ea48610d43 ("clk: hi6220: Clock driver support for Hisilicon hi6220 SoC")
> Signed-off-by: Leo Yan <leo.yan@linaro.org>
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-09-01 1:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 7:58 [PATCH 1/2] clk: hi6220: change watchdog clock source Leo Yan
2017-08-29 7:58 ` Leo Yan
2017-08-29 7:58 ` [PATCH 2/2] arm64: dts: hi6220: enable watchdog Leo Yan
2017-08-29 7:58 ` Leo Yan
2017-09-01 1:32 ` Stephen Boyd
2017-09-01 1:32 ` Stephen Boyd
2017-09-01 10:35 ` Wei Xu
2017-09-01 10:35 ` Wei Xu
2017-09-01 10:35 ` Wei Xu
2017-09-01 20:28 ` Stephen Boyd
2017-09-01 20:28 ` Stephen Boyd
2017-09-04 9:21 ` Wei Xu
2017-09-04 9:21 ` Wei Xu
2017-09-04 9:21 ` Wei Xu
2017-09-01 1:32 ` Stephen Boyd [this message]
2017-09-01 1:32 ` [PATCH 1/2] clk: hi6220: change watchdog clock source Stephen Boyd
2017-09-01 2:16 ` Leo Yan
2017-09-01 2:16 ` 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=20170901013240.GM21656@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=dimitrysh@google.com \
--cc=guodong.xu@linaro.org \
--cc=haojian.zhuang@linaro.org \
--cc=leo.yan@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=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 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.