From: Magnus Damm <magnus.damm@gmail.com>
To: linux-sh@vger.kernel.org
Subject: [PATCH 00/10] ARM: shmobile: shmobile_init_delay() conversion
Date: Wed, 20 Aug 2014 12:59:49 +0000 [thread overview]
Message-ID: <20140820130201.32075.45257.sendpatchset@w520> (raw)
ARM: shmobile: shmobile_init_delay() conversion
[PATCH 01/10] ARM: shmobile: sh7372: Update DTS to include CPU frequency
[PATCH 02/10] ARM: shmobile: sh73a0: Update DTS to include CPU frequency
[PATCH 03/10] ARM: shmobile: r8a7778: Update DTS to include CPU frequency
[PATCH 04/10] ARM: shmobile: sh7372: Use shmobile_init_delay()
[PATCH 05/10] ARM: shmobile: sh73a0: Use shmobile_init_delay()
[PATCH 06/10] ARM: shmobile: r8a7778: Use shmobile_init_delay()
[PATCH 07/10] ARM: shmobile: r8a73a4: Use shmobile_init_delay()
[PATCH 08/10] ARM: shmobile: Remove shmobile_setup_delay()
[PATCH 09/10] ARM: shmobile: bockw: Use shmobile_init_delay()
[PATCH 10/10] ARM: shmobile: kzm9g: Use shmobile_init_delay()
Convert the ARM mach-shmobile subarch to use shmobile_init_delay()
together with CPU Frequency information in DTS instead of specifying
these things in C. Remove the now redundant shmobile_setup_delay().
Merge-wise, for this to remain bisectable patch 1-3 needs to be merged
first (DTS) - any order is however fine. After that patch 4-7 can be
applied in any order (SoC) followed by any order of the last patches
8-10 (core + board).
After this one more SoC series is needed to remove local now unused
delay functions, but it needs to happen after the board code in patch
9 and 10 are merged, so to avoid cicular dependecy this has been
omitted for now.
Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
---
Written on top of renesas-devel-20140820-v3.17-rc1
Untested, but should be safe enough. Seems to build with shmobile_defconfig.
arch/arm/boot/dts/r8a7778.dtsi | 6 ++++++
arch/arm/boot/dts/sh7372.dtsi | 1 +
arch/arm/boot/dts/sh73a0.dtsi | 2 ++
arch/arm/mach-shmobile/board-bockw-reference.c | 2 +-
arch/arm/mach-shmobile/board-bockw.c | 2 +-
arch/arm/mach-shmobile/board-kzm9g-reference.c | 2 +-
arch/arm/mach-shmobile/common.h | 2 --
arch/arm/mach-shmobile/r8a73a4.h | 1 -
arch/arm/mach-shmobile/setup-r8a73a4.c | 9 +--------
arch/arm/mach-shmobile/setup-r8a7778.c | 2 +-
arch/arm/mach-shmobile/setup-sh7372.c | 2 +-
arch/arm/mach-shmobile/setup-sh73a0.c | 2 +-
arch/arm/mach-shmobile/timer.c | 21 ++-------------------
13 files changed, 18 insertions(+), 36 deletions(-)
next reply other threads:[~2014-08-20 12:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 12:59 Magnus Damm [this message]
2014-08-22 2:23 ` [PATCH 00/10] ARM: shmobile: shmobile_init_delay() conversion 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=20140820130201.32075.45257.sendpatchset@w520 \
--to=magnus.damm@gmail.com \
--cc=linux-sh@vger.kernel.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).