All of lore.kernel.org
 help / color / mirror / Atom feed
From: ben.dooks@codethink.co.uk (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] arm: Add basic support for new Marvell Armada 370 and Armada XP SoC
Date: Wed, 27 Jun 2012 09:57:13 +0100	[thread overview]
Message-ID: <4FEACAE9.2080901@codethink.co.uk> (raw)
In-Reply-To: <1340699313-29331-1-git-send-email-gregory.clement@free-electrons.com>

On 26/06/12 09:28, Gregory Clement wrote:
>
> Arnd, Olof,
>
> You'll find in this patch set the third version of the initial support
> for a new family of ARMv7-compatible Marvell SoCs.
>
> As for the previous releases, both the Armada 370 and the Armada XP
> SoCs are supported in this directory, and we are able to build a
> single kernel image that boots on both SoCs. Both SoCs use the PJ4B
> processor, a Marvell-developed ARM core that implements the ARMv7
> instruction set. We are currently using Marvell evaluation boards for
> both of those SoCs, and the support for those boards is added in this
> patch set.
>
> We remained focused on a limited preliminary support which only
> includes the necessary code for timer and IRQ support, the serial
> controller is a standard 16550-compatible one. The diffstat looks
> like:
>
>   Documentation/devicetree/bindings/arm/armada-370-xp-mpic.txt      |   23 +
>   Documentation/devicetree/bindings/arm/armada-370-xp-timer.txt     |   11 +
>   Documentation/devicetree/bindings/arm/armada-370-xp.txt           |   24 +
>   Documentation/devicetree/bindings/arm/mvebu-system-controller.txt |   16 +
>   MAINTAINERS                                                       |    8 +
>   arch/arm/Kconfig                                                  |   14 +
>   arch/arm/Makefile                                                 |    1 +
>   arch/arm/boot/dts/armada-370-db.dts                               |   42 +
>   arch/arm/boot/dts/armada-370-xp.dtsi                              |   68 ++
>   arch/arm/boot/dts/armada-370.dtsi                                 |   35 +
>   arch/arm/boot/dts/armada-xp-db.dts                                |   50 +
>   arch/arm/boot/dts/armada-xp.dtsi                                  |   55 +
>   arch/arm/configs/mvebu_defconfig                                  |   46 +
>   arch/arm/mach-mvebu/Kconfig                                       |   16 +
>   arch/arm/mach-mvebu/Makefile                                      |    2 +
>   arch/arm/mach-mvebu/Makefile.boot                                 |    1 +
>   arch/arm/mach-mvebu/armada-370-xp.c                               |   63 ++
>   arch/arm/mach-mvebu/common.h                                      |   23 +
>   arch/arm/mach-mvebu/include/mach/armada-370-xp.h                  |   22 +
>   arch/arm/mach-mvebu/include/mach/debug-macro.S                    |   24 +
>   arch/arm/mach-mvebu/include/mach/timex.h                          |   13 +
>   arch/arm/mach-mvebu/include/mach/uncompress.h                     |   43 +
>   arch/arm/mach-mvebu/irq-armada-370-xp.c                           |  133 +++
>   arch/arm/mach-mvebu/system-controller.c                           |  105 ++
>   drivers/clocksource/Kconfig                                       |    3 +
>   drivers/clocksource/Makefile                                      |    3 +-
>   drivers/clocksource/time-armada-370-xp.c                          |  242 +++++
>   include/linux/time-armada-370-xp.h                                |   18 +
>   28 files changed, 1103 insertions(+), 1 deletion(-)
>
> This patch set, and the support for those SoCs, started as a
> collaborative effort from Marvell engineers (who have done the initial
> development work) and Free Electrons engineers (who are reshaping the
> code for mainline submission, adding device tree support, etc.). This
> effort has also received contributions from Ben Dooks from Codethink.
>
> The patch set is based on your arm-soc/for-next branch (updated on Monday
> 25th June).

Where should I pull from to have a test?

-- 
Ben Dooks				http://www.codethink.co.uk/
Senior Engineer				Codethink - Providing Genius

  parent reply	other threads:[~2012-06-27  8:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-26  8:28 [PATCH v4] arm: Add basic support for new Marvell Armada 370 and Armada XP SoC Gregory Clement
2012-06-26  8:28 ` [PATCH v4 1/9] clocksource: time-armada-370-xp: Marvell Armada 370/XP SoC timer driver Gregory Clement
2012-06-26  8:28 ` [PATCH v4 2/9] arm: mach-mvebu: add header Gregory Clement
2012-06-26  8:28 ` [PATCH v4 3/9] arm: mach-mvebu: add source files Gregory Clement
2012-06-26  8:47   ` Andrew Lunn
2012-06-26 10:05     ` Gregory CLEMENT
2012-06-26 10:21       ` Andrew Lunn
2012-06-26 16:17   ` Arnd Bergmann
2012-06-27  7:52     ` Gregory CLEMENT
2012-06-27  9:02     ` Ben Dooks
2012-06-26  8:28 ` [PATCH v4 4/9] arm: mach-mvebu: add support for Armada 370 and Armada XP with DT Gregory Clement
2012-06-26  8:28 ` [PATCH v4 5/9] arm: mach-mvebu: add documentation for new device tree bindings Gregory Clement
2012-06-26  8:53   ` Andrew Lunn
2012-06-26  9:42     ` Gregory CLEMENT
2012-06-26  8:28 ` [PATCH v4 6/9] arm: mach-mvebu: add defconfig Gregory Clement
2012-06-26  8:28 ` [PATCH v4 7/9] arm: mach-mvebu: add compilation/configuration change Gregory Clement
2012-06-26  8:28 ` [PATCH v4 8/9] arm: mach-mvebu: add entry to MAINTAINERS Gregory Clement
2012-06-26  8:28 ` [PATCH v4 9/9] ARM: mvebu: MPIC: read number of interrupts from control register Gregory Clement
2012-06-27  8:57 ` Ben Dooks [this message]
2012-06-27  9:03   ` [PATCH v4] arm: Add basic support for new Marvell Armada 370 and Armada XP SoC Gregory CLEMENT

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=4FEACAE9.2080901@codethink.co.uk \
    --to=ben.dooks@codethink.co.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.