From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: i.MX: Convert v4/v5 based SoCs to common clock framework
Date: Mon, 19 Mar 2012 09:44:41 -0500 [thread overview]
Message-ID: <4F674659.40207@gmail.com> (raw)
In-Reply-To: <1332164166-6055-1-git-send-email-s.hauer@pengutronix.de>
On 03/19/2012 08:35 AM, Sascha Hauer wrote:
> Hi All,
>
> The following patches convert the i.MX v4/v5 based SoCs to the common
> clock framework. They may not be completely ready, I am posting it now
> because I'd like to show that the function based clock initializers are
> indeed usable in real life and that the end result does not look too
> bad.
>
> This series depends on another series not yet posted which convert the
> i.MX drivers to not depend on grouped clocks. I will follow up on this
> after the merge window. My plan for these patches is to put them into
> the arm-soc staging area after the merge window to let them stabilize
> until hopefully before the next merge window there are no regressions
> left.
>
> Except the i.MX21 port all SoCs are runtime tested with the basic
> devices (at least uart and network; I tested more, but not
> systematically). Testers for these patches are very welcome, I will
> happily integrate fixups into this series. A branch containing Mikes
> latest clock patches, the driver fixups and this series can be found
> here:
>
> git://git.pengutronix.de/git/imx/linux-2.6.git work/imx-clk-v4-v5
>
> As a side note, we currently compile all i.MX v4/v5 based SoCs in a
> single defconfig. Since a kernel can only be built with or without the
> common clock framework this series is not fully bisectable, you have to
> disable the not yet converted SoCs in between.
>
> The patch for removing the old clock support is not included in this
> post, but with the removal the overall diffstat looks like this:
>
> arch/arm/mach-imx/clock-imx1.c | 636 ---------------
> arch/arm/mach-imx/clock-imx21.c | 1239 -------------------------------
> arch/arm/mach-imx/clock-imx25.c | 346 --------
> arch/arm/mach-imx/clock-imx27.c | 766 -------------------
> b/arch/arm/mach-imx/Kconfig | 4
> b/arch/arm/mach-imx/Makefile | 10
> b/arch/arm/mach-imx/clk-imx1.c | 118 ++
> b/arch/arm/mach-imx/clk-imx21.c | 177 ++++
> b/arch/arm/mach-imx/clk-imx25.c | 242 ++++++
> b/arch/arm/mach-imx/clk-imx27.c | 277 ++++++
> b/arch/arm/mach-imx/clk-pllv1.c | 59 +
> b/arch/arm/mach-imx/clk.h | 44 +
> b/arch/arm/plat-mxc/clock.c | 11
> b/arch/arm/plat-mxc/include/mach/clock.h | 4
> b/arch/arm/plat-mxc/time.c | 5
> 15 files changed, 946 insertions(+), 2992 deletions(-)
>
> ----------------------------------------------------------------
> Sascha Hauer (7):
> ARM i.MX: prepare for common clock framework
> ARM i.MX timer: request correct clock
> ARM i.MX: Add common clock support for pllv1
> ARM i.MX1: implement clocks using common clock framework
> ARM i.MX21: implement clocks using common clock framework
> ARM i.MX25: implement clocks using common clock framework
> ARM i.MX27: implement clocks using common clock framework
>
> arch/arm/mach-imx/Kconfig | 4 +
> arch/arm/mach-imx/Makefile | 10 +-
> arch/arm/mach-imx/clk-imx1.c | 118 ++++++++++++++
> arch/arm/mach-imx/clk-imx21.c | 177 ++++++++++++++++++++
> arch/arm/mach-imx/clk-imx25.c | 242 ++++++++++++++++++++++++++++
> arch/arm/mach-imx/clk-imx27.c | 277 ++++++++++++++++++++++++++++++++
> arch/arm/mach-imx/clk-pllv1.c | 59 +++++++
> arch/arm/mach-imx/clk.h | 44 +++++
> arch/arm/plat-mxc/clock.c | 11 ++
> arch/arm/plat-mxc/include/mach/clock.h | 4 +
> arch/arm/plat-mxc/time.c | 5 +-
> 11 files changed, 946 insertions(+), 5 deletions(-)
> create mode 100644 arch/arm/mach-imx/clk-imx1.c
> create mode 100644 arch/arm/mach-imx/clk-imx21.c
> create mode 100644 arch/arm/mach-imx/clk-imx25.c
> create mode 100644 arch/arm/mach-imx/clk-imx27.c
> create mode 100644 arch/arm/mach-imx/clk-pllv1.c
> create mode 100644 arch/arm/mach-imx/clk.h
>
Do we want to move all clock code to drivers/clk? I'm not saying it has
to be done now, but is that a goal?
Rob
next prev parent reply other threads:[~2012-03-19 14:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 13:35 i.MX: Convert v4/v5 based SoCs to common clock framework Sascha Hauer
2012-03-19 13:35 ` [PATCH 1/8] clk: add a fixed factor clock Sascha Hauer
2012-03-23 7:37 ` Philipp Zabel
2012-03-23 8:40 ` Sascha Hauer
2012-03-23 7:41 ` Philipp Zabel
2012-03-23 8:42 ` Sascha Hauer
2012-03-19 13:36 ` [PATCH 2/8] ARM i.MX: prepare for common clock framework Sascha Hauer
2012-03-19 13:36 ` [PATCH 3/8] ARM i.MX timer: request correct clock Sascha Hauer
2012-03-19 13:36 ` [PATCH 4/8] ARM i.MX: Add common clock support for pllv1 Sascha Hauer
2012-03-19 13:36 ` [PATCH 5/8] ARM i.MX1: implement clocks using common clock framework Sascha Hauer
2012-03-19 13:36 ` [PATCH 6/8] ARM i.MX21: " Sascha Hauer
2012-03-19 13:36 ` [PATCH 7/8] ARM i.MX25: " Sascha Hauer
2012-03-19 13:36 ` [PATCH 8/8] ARM i.MX27: " Sascha Hauer
2012-03-19 14:23 ` Shawn Guo
2012-03-19 14:36 ` Sascha Hauer
2012-03-19 16:17 ` Arnd Bergmann
2012-03-19 14:44 ` Rob Herring [this message]
2012-03-20 23:27 ` i.MX: Convert v4/v5 based SoCs to " Turquette, Mike
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=4F674659.40207@gmail.com \
--to=robherring2@gmail.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).