From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V5 0/5] clk: mmp: add clock framework for mmp
Date: Wed, 29 Aug 2012 11:26:39 -0700 [thread overview]
Message-ID: <20120829182639.4450.99900@nucleus> (raw)
In-Reply-To: <CADApbehotHB7JSCHdo_eoTb08C5Pe6ewh7whwckQTyuCcMM=BQ@mail.gmail.com>
Quoting Chao Xie (2012-08-26 18:19:02)
> On Sat, Aug 25, 2012 at 8:21 AM, Mike Turquette <mturquette@linaro.org> wrote:
> > Quoting Chao Xie (2012-08-19 19:55:10)
> >> From: Chao Xie <chao.xie@marvell.com>
> >> arch/arm/mach-mmp/Kconfig | 3 +
> >> drivers/clk/Makefile | 3 +
> >> drivers/clk/mmp/Makefile | 9 +
> >> drivers/clk/mmp/clk-apbc.c | 152 ++++++++++++++
> >> drivers/clk/mmp/clk-apmu.c | 97 +++++++++
> >> drivers/clk/mmp/clk-frac.c | 153 ++++++++++++++
> >> drivers/clk/mmp/clk-mmp2.c | 449 ++++++++++++++++++++++++++++++++++++++++++
> >> drivers/clk/mmp/clk-pxa168.c | 346 ++++++++++++++++++++++++++++++++
> >> drivers/clk/mmp/clk-pxa910.c | 320 ++++++++++++++++++++++++++++++
> >> drivers/clk/mmp/clk.h | 35 ++++
> >
> > Looks like you are not removing your arch/arm/mach-mmp/clock.c. Is that
> > intentional?
> >
> > When I apply your series against v3.6-rc3 I find that compilation breaks
> > with mmp2_defconfig due to conflicting definitions for the clk api
> > (clk_enable, clk_set_rate, etc). This is not surprising since your
> > legacy clock code is neither deleted nor removed from compilation
> > conditionally by checking for CONFIG_COMMON_CLK.
> >
> > Did I somehow manage to misapply your patches or should your patches
> > have removed the arch-specific clock framework as well?
> >
> hi, Mike
> Yes. There are some patches for seperate the original clock code in arch.
> I had sent these patches before, but it seems that too many patches
> sent, and haojian missed it.
> I will sent out the patches for arch today. Thanks.
>
I pulled in the dependency series and the build goes through nicely now.
I'm happy to take these five patches into clk-next but of course mmp
will have problems building clk-next without the dependencies, which I
assume are going through arm-soc.
Regards,
Mike
> > Regards,
> > Mike
> >
> >> 10 files changed, 1567 insertions(+), 0 deletions(-)
> >> create mode 100644 drivers/clk/mmp/Makefile
> >> create mode 100644 drivers/clk/mmp/clk-apbc.c
> >> create mode 100644 drivers/clk/mmp/clk-apmu.c
> >> create mode 100644 drivers/clk/mmp/clk-frac.c
> >> create mode 100644 drivers/clk/mmp/clk-mmp2.c
> >> create mode 100644 drivers/clk/mmp/clk-pxa168.c
> >> create mode 100644 drivers/clk/mmp/clk-pxa910.c
> >> create mode 100644 drivers/clk/mmp/clk.h
next prev parent reply other threads:[~2012-08-29 18:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 2:55 [PATCH V5 0/5] clk: mmp: add clock framework for mmp Chao Xie
2012-08-20 2:55 ` [PATCH V5 1/5] clk: mmp: add mmp specific clocks Chao Xie
2012-08-20 2:55 ` [PATCH V5 2/5] clk: mmp: add clock definition for pxa168 Chao Xie
2012-08-20 2:55 ` [PATCH V5 3/5] clk: mmp: add clock definition for pxa910 Chao Xie
2012-08-20 2:55 ` [PATCH V5 4/5] clk: mmp: add clock definition for mmp2 Chao Xie
2012-08-20 2:55 ` [PATCH V5 5/5] arm: mmp: make all SOCs use common clock by default Chao Xie
2012-08-20 5:39 ` [PATCH V5 0/5] clk: mmp: add clock framework for mmp Arnd Bergmann
2012-08-25 0:21 ` Mike Turquette
2012-08-27 1:19 ` Chao Xie
2012-08-29 18:26 ` Mike Turquette [this message]
2012-09-11 5:54 ` Chao Xie
2012-09-11 13:33 ` Haojian Zhuang
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=20120829182639.4450.99900@nucleus \
--to=mturquette@linaro.org \
--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).