From: takasi-y@ops.dti.ne.jp
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] ARM: shmobile: kzm9d: migrate to common clock framework with DT
Date: Tue, 08 Oct 2013 05:30:40 +0000 [thread overview]
Message-ID: <20131008143040.52f36df8edb7ab63224d8433@ops.dti.ne.jp> (raw)
This patch series makes kzm9d to move to new clk implementation
based on the common clock framework and device tree, when configured
as a part of multi-platform.
These patches do not remove sh-clkfwk version, even on emev2.
Non multi-platform configuration still uses sh-clkfwk.
Should be applied and compiled on
kernel/git/horms/renesas.git tag:renesas-devel-20131008
Confirmed for boot up to command prompt.
- kzm9d board / multi-platform + kzm9d configuration
- kzm9d board / kzm9d configuration for regression
for compilation
- ape6evm(non-multi-platform) configuration for regression.
Changes since v1:
Generally, simplified, depending on
[PATCH 00/05] ARM: shmobile: KZM9D Multiplatform update
series posted recently by Magnus.
[PATCH 1/6] clocksource: em_sti: convert to clk_prepare/unprepare
[PATCH 2/6] serial8250-em: convert to clk_prepare/unprepare
Removed because the new base includes it.
Thank you for your review, Daniel, Greg, Laurent, and Magnus.
[PATCH 3/6] sh: clkfwk: Select sh-/common- clkfwk alternatively
Removed because "KZM9D Multiplatform update" had made this not needed.
[PATCH v2 1/3] clk: emev2: Add support for emev2 SMU clocks with DT
[PATCH v2 2/3] ARM: shmobile: emev2: Add clock tree description in DT
(was 3/6, 4/6)
Add @unit-address to smu in dts.
Reassemble patches to (.txt + .c) + .dts from .txt + (.c + .dts).
Only used when multi-platform configuration.
Extra blank line removed.
[PATCH v2 3/3] ARM: shmobile: kzm9d: Use common clock framework
(was 6/6)
No Kconfig modification because of "KZM9D Multiplatform update".
Takashi YOSHII (3):
clk: emev2: Add support for emev2 SMU clocks with DT
ARM: shmobile: emev2: Add clock tree description in DT
ARM: shmobile: kzm9d: Use common clock framework
.../devicetree/bindings/clock/emev2-clock.txt | 98 +++++++++++++++++++
arch/arm/boot/dts/emev2.dtsi | 84 +++++++++++++++++
arch/arm/mach-shmobile/board-kzm9d-reference.c | 5 +-
next reply other threads:[~2013-10-08 5:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 5:30 takasi-y [this message]
2013-10-08 5:32 ` [PATCH v2 1/3] clk: emev2: Add support for emev2 SMU clocks with DT takasi-y
2013-10-08 5:58 ` Magnus Damm
2013-10-09 3:38 ` Simon Horman
2013-10-09 6:10 ` Ben Dooks
2013-10-08 5:33 ` [PATCH v2 2/3] ARM: shmobile: emev2: Add clock tree description in DT takasi-y
2013-10-08 5:54 ` Magnus Damm
2013-10-09 3:40 ` Simon Horman
2013-10-08 5:34 ` [PATCH v2 3/3] ARM: shmobile: kzm9d: Use common clock framework takasi-y
2013-10-08 5:52 ` Magnus Damm
2013-10-09 3:40 ` Simon Horman
2013-10-09 4:59 ` Magnus Damm
2013-10-09 6:54 ` Simon Horman
2013-10-09 7:29 ` Magnus Damm
2013-10-09 10:39 ` Simon Horman
2013-10-29 4:42 ` Simon Horman
2013-12-02 2:25 ` Simon Horman
2013-12-23 6:41 ` Mike Turquette
2013-12-23 8:00 ` Simon Horman
2014-01-06 8:10 ` Simon Horman
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=20131008143040.52f36df8edb7ab63224d8433@ops.dti.ne.jp \
--to=takasi-y@ops.dti.ne.jp \
--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).