From: Leo Yan <leo.yan@linaro.org>
To: Amit Kucheria <amit.kucheria@verdurent.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Jiancheng Xue <xuejiancheng@hisilicon.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Rob Herring <robh@kernel.org>,
linux-clk@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Guodong Xu <guodong.xu@linaro.org>
Subject: Re: [PATCH] clk: Hi6220: enable stub clock driver for ARCH_HISI
Date: Mon, 8 Aug 2016 23:32:20 +0800 [thread overview]
Message-ID: <20160808153220.GB5285@leoy-linaro> (raw)
In-Reply-To: <CAHLCerObKvK2KZRQFWk2BpjEiRSskwUNs4csMMNRQGmjHF8nhg@mail.gmail.com>
On Mon, Aug 08, 2016 at 08:12:21PM +0530, Amit Kucheria wrote:
[...]
> >> > diff --git a/drivers/clk/hisilicon/Kconfig b/drivers/clk/hisilicon/Kconfig
> >> > index 3f537a0..9e0a95e 100644
> >> > --- a/drivers/clk/hisilicon/Kconfig
> >> > +++ b/drivers/clk/hisilicon/Kconfig
> >> > @@ -23,5 +23,6 @@ config RESET_HISI
> >> > config STUB_CLK_HI6220
> >> > bool "Hi6220 Stub Clock Driver"
> >> > depends on COMMON_CLK_HI6220 && MAILBOX
> >> > + default ARCH_HISI
>
> Instead of forcing this up on the entire arch, why not restrict it to
> just the cpufreq driver? ARM_HISI_ACPU_CPUFREQ?
ARM_HISI_ACPU_CPUFREQ has been removed by 3920be471ce7f "cpufreq:
hisilicon: Use generic platdev driver". By default now platforms are
using drivers/cpufreq/cpufreq-dt-platdev.c.
> >> > help
> >> > Build the Hisilicon Hi6220 stub clock driver.
> >> > --
> >> > 1.9.1
> >> >
next prev parent reply other threads:[~2016-08-08 15:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 3:37 [PATCH] clk: Hi6220: enable stub clock driver for ARCH_HISI Leo Yan
2016-08-08 5:53 ` Amit Kucheria
2016-08-08 6:42 ` Leo Yan
2016-08-08 14:42 ` Amit Kucheria
2016-08-08 15:32 ` Leo Yan [this message]
2016-08-08 15:53 ` Daniel Thompson
2016-08-08 18:02 ` Amit Kucheria
2016-08-08 20:36 ` Daniel Thompson
2016-08-09 1:23 ` 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=20160808153220.GB5285@leoy-linaro \
--to=leo.yan@linaro.org \
--cc=amit.kucheria@verdurent.com \
--cc=dietmar.eggemann@arm.com \
--cc=guodong.xu@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=xuejiancheng@hisilicon.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