From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 3/3] clk: keystone: Build Keystone clock drivers
Date: Tue, 8 Oct 2013 09:05:23 -0400 [thread overview]
Message-ID: <52540313.1040205@ti.com> (raw)
In-Reply-To: <20131008012859.7445.26447@quantum>
On Monday 07 October 2013 09:28 PM, Mike Turquette wrote:
> Quoting Santosh Shilimkar (2013-09-25 18:18:15)
>> Now build the keystone common clock drivers. The build is made
>> conditional based on COMMON_CLK_KEYSTONE
>>
>> Cc: Mike Turquette <mturquette@linaro.org>
>>
>> Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
>> ---
>> drivers/clk/Kconfig | 7 +++++++
>> drivers/clk/Makefile | 1 +
>> drivers/clk/keystone/Makefile | 1 +
>> 3 files changed, 9 insertions(+)
>> create mode 100644 drivers/clk/keystone/Makefile
>>
>> diff --git a/drivers/clk/Kconfig b/drivers/clk/Kconfig
>> index 279407a..10f85cc 100644
>> --- a/drivers/clk/Kconfig
>> +++ b/drivers/clk/Kconfig
>> @@ -93,6 +93,13 @@ config CLK_PPC_CORENET
>> This adds the clock driver support for Freescale PowerPC corenet
>> platforms using common clock framework.
>>
>> +config COMMON_CLK_KEYSTONE
>> + tristate "Clock drivers for Keystone based SOCs"
>> + depends on ARCH_KEYSTONE && OF
>> + ---help---
>> + Supports clock drivers for Keystone based SOCs. These SOCs have local
>> + a power sleep control module that gate the clock to the IPs and PLLs.
>> +
>> endmenu
>>
>> source "drivers/clk/mvebu/Kconfig"
>> diff --git a/drivers/clk/Makefile b/drivers/clk/Makefile
>> index 7b11106..2a44d533 100644
>> --- a/drivers/clk/Makefile
>> +++ b/drivers/clk/Makefile
>> @@ -32,6 +32,7 @@ obj-$(CONFIG_ARCH_VT8500) += clk-vt8500.o
>> obj-$(CONFIG_ARCH_ZYNQ) += zynq/
>> obj-$(CONFIG_ARCH_TEGRA) += tegra/
>> obj-$(CONFIG_PLAT_SAMSUNG) += samsung/
>> +obj-$(CONFIG_COMMON_CLK_KEYSTONE) += keystone/
>
> Thanks for respinning these patches Santosh. They look good and I've
> taken them into clk-next for 3.13.
>
Great.
> My only question: why CONFIG_COMMON_CLK_KEYSTONE and not just
> CONFIG_ARCH_KEYSTONE above? This is not a blocking issue and can be
> revisited later.
>
The clock Kconfig had few arch using directly ARCH defines as few creating
arch CCF. I gone ahead with CCF bunch. Probably we can just make that
consistent for all other arch in future as you said.
Thanks a lot Mike.
Regards,
Santosh
prev parent reply other threads:[~2013-10-08 13:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-26 1:18 [PATCH v3 0/3] clk: keystone: Add common clock drivers Santosh Shilimkar
2013-09-26 1:18 ` [PATCH v3 1/3] clk: keystone: add Keystone PLL clock driver Santosh Shilimkar
2013-09-26 1:18 ` [PATCH v3 2/3] clk: keystone: Add gate control " Santosh Shilimkar
2013-09-26 1:18 ` [PATCH v3 3/3] clk: keystone: Build Keystone clock drivers Santosh Shilimkar
2013-10-08 1:28 ` Mike Turquette
2013-10-08 13:05 ` Santosh Shilimkar [this message]
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=52540313.1040205@ti.com \
--to=santosh.shilimkar@ti.com \
--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).