From: mturquette@ti.com (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/5] ARM: at91: Implementation of PMC clks using the common clk framework.
Date: Tue, 12 Jun 2012 10:03:06 -0700 [thread overview]
Message-ID: <20120612170306.GD19410@gmail.com> (raw)
In-Reply-To: <1336812838-3649-3-git-send-email-linux-arm@overkiz.com>
On 20120512-10:53, Boris BREZILLON wrote:
> diff --git a/arch/arm/mach-at91/Makefile b/arch/arm/mach-at91/Makefile
> index 79d0f60..29f8812 100644
> --- a/arch/arm/mach-at91/Makefile
> +++ b/arch/arm/mach-at91/Makefile
> @@ -6,8 +6,11 @@ obj-y := irq.o gpio.o setup.o
> obj-m :=
> obj-n :=
> obj- :=
> -
> +ifeq ($(CONFIG_COMMON_CLK),y)
> +obj-$(CONFIG_AT91_PMC_UNIT) += pmc-osc.o pmc-pll.o pmc-master.o pmc-sys.o pmc-periph.o pmc-prog.o pmc.o
> +else
> obj-$(CONFIG_AT91_PMC_UNIT) += clock.o
> +endif
Hi Boris,
Looks like the old platform clock code is not removed in this series.
Is this just a work in progress or do you want to merge in AT91 support
for common clk while leaving the old clock code merged in?
Regards,
Mike
next prev parent reply other threads:[~2012-06-12 17:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-12 8:53 [PATCH 0/5] ARM: at91: moving at91 to the common clk framework Boris BREZILLON
2012-05-12 8:53 ` [PATCH 1/5] ARM: at91: Add PMC registers definitions Boris BREZILLON
2012-05-12 8:53 ` [PATCH 2/5] ARM: at91: Implementation of PMC clks using the common clk framework Boris BREZILLON
2012-06-12 17:03 ` Mike Turquette [this message]
2012-06-14 11:48 ` Boris BREZILLON
2012-05-12 8:53 ` [PATCH 3/5] ARM: at91: disable specific soc clock init functions Boris BREZILLON
2012-05-12 8:53 ` [PATCH 4/5] ARM: at91: add pmc clks definition into device tree Boris BREZILLON
2012-05-12 8:53 ` [PATCH 5/5] ARM: at91: Modify board_dt init sequence Boris BREZILLON
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=20120612170306.GD19410@gmail.com \
--to=mturquette@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).