linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: magnus.damm@gmail.com (Magnus Damm)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/04] ARM: shmobile: r8a73a4 SoC support V3
Date: Tue, 26 Mar 2013 10:34:14 +0900	[thread overview]
Message-ID: <20130326013414.11796.9937.sendpatchset@w520> (raw)

ARM: shmobile: r8a73a4 SoC support V3
[PATCH 01/04] ARM: shmobile: Initial r8a73a4 SoC support V3
[PATCH 02/04] ARM: shmobile: r8a73a4 SCIF support V3
[PATCH 03/04] ARM: shmobile: r8a73a4 IRQC support V2
[PATCH 04/04] ARM: shmobile: r8a73a4 PFC support

This series is V3 of initial support for the r8a73a4 SoC. The SoC
is known as r8a73a4 which is built around Cortex-A15 and makes use
of SCIF for serial, IRQC interrupt controller for external IRQs and
PFC for combined support for pinmux and GPIO.

Changes in V3:
- Added clock mapping for all supported root clocks
- Fixed a bug in the SCIF patch where PORT_SCIFA was always being selected

Updated PFC and APE6EVM series will be on top of this one.

Signed-off-by: Magnus Damm <damm@opensource.se>
---

 Written against "next" renesas.git 442d651d3764ba4203c6b766a1ddd3ac24a40410
 [PATCH 01/04] requires [PATCH] ARM: shmobile: Disallow PINCTRL without GPIOLIB
 [PATCH 03/04] requires the IRQC driver to build

 arch/arm/boot/dts/r8a73a4.dtsi                |   87 +++++++++++
 arch/arm/mach-shmobile/Kconfig                |    9 +
 arch/arm/mach-shmobile/Makefile               |    1 
 arch/arm/mach-shmobile/clock-r8a73a4.c        |  106 ++++++++++++++
 arch/arm/mach-shmobile/include/mach/r8a73a4.h |    8 +
 arch/arm/mach-shmobile/setup-r8a73a4.c        |  187 +++++++++++++++++++++++++
 6 files changed, 397 insertions(+), 1 deletion(-)

             reply	other threads:[~2013-03-26  1:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26  1:34 Magnus Damm [this message]
2013-03-26  1:34 ` [PATCH 01/04] ARM: shmobile: Initial r8a73a4 SoC support V3 Magnus Damm
2013-03-26  1:34 ` [PATCH 02/04] ARM: shmobile: r8a73a4 SCIF " Magnus Damm
2013-03-26  1:34 ` [PATCH 03/04] ARM: shmobile: r8a73a4 IRQC support V2 Magnus Damm
2013-03-26  1:34 ` [PATCH 04/04] ARM: shmobile: r8a73a4 PFC support Magnus Damm
2013-03-26  6:17 ` [PATCH 0/1] ARM: shmobile: r8a73a4 thermal support Kuninori Morimoto
2013-03-26  6:18   ` [PATCH] ARM: shmobile: r8a73a4: add thermal driver support Kuninori Morimoto
2013-03-27  5:17     ` Simon Horman
2013-03-27  9:19       ` Magnus Damm
2013-03-27 12:11     ` Simon Horman
2013-03-27  5:21   ` [PATCH 0/1] ARM: shmobile: r8a73a4 thermal support Simon Horman
2013-03-27  7:49     ` Kuninori Morimoto
2013-03-27  9:17     ` Magnus Damm
2013-03-27 12:09       ` Simon Horman
2013-03-27 12:10       ` Simon Horman
2013-03-26 11:48 ` [PATCH 00/04] ARM: shmobile: r8a73a4 SoC support V3 Arnd Bergmann
2013-03-26 14:17   ` Magnus Damm
2013-03-27  3:46     ` Simon Horman
2013-03-27  8:19       ` Magnus Damm
2013-03-27 11:45         ` Simon Horman
2013-03-27 12:01           ` Simon Horman
2013-03-27 16:37             ` Magnus Damm

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=20130326013414.11796.9937.sendpatchset@w520 \
    --to=magnus.damm@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).