linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ben.dooks@codethink.co.uk (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5] arm: Add basic support for new Marvell Armada 370 and Armada XP SoC
Date: Wed, 27 Jun 2012 16:54:43 +0100	[thread overview]
Message-ID: <4FEB2CC3.7090305@codethink.co.uk> (raw)
In-Reply-To: <1340805290-9051-1-git-send-email-gregory.clement@free-electrons.com>

On 27/06/12 14:54, Gregory Clement wrote:
> Arnd, Olof,
>
> You'll find in this patch set the fifth version of the initial support
> for a new family of ARMv7-compatible Marvell SoCs.
>
> Do you think this patch set has a chance of hitting the 3.6 merge
> window ?
>
> We are willing to quickly resubmit updated versions to take into
> account new comments. We have a lot more code to support those new
> SoCs, and we would like to make progress in submitting those other
> parts for the mainline.
>
> 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 |   17 +
>   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                           |  100 ++
>   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, 1099 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.

It may be something wrong in my device-tree setup, but this is not
booting for me:

> Uncompressing Linux... done, booting the kernel.
> <6>Booting Linux on physical CPU 0
> <5>Linux version 3.5.0-rc4-11036-g90ad2b7-dirty (ben at rainbowdash) (gcc version 4.4.52
> CPU: ARMv7 Processor [562f5842] revision 2 (ARMv7), cr=10c53c7d
> CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
> <6>Machine: Marvell Aramada 370/XP (Device Tree), model: Cogent CSB1726 SoM
> Memory policy: ECC disabled, Data cache writeback
> <0>Kernel panic - not syncing: ERROR: Failed to allocate 0x1000 bytes below 0x0.

This is the last thing I get before it stops. Any ideas on what went
wrong?

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

  parent reply	other threads:[~2012-06-27 15:54 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-27 13:54 [PATCH v5] arm: Add basic support for new Marvell Armada 370 and Armada XP SoC Gregory Clement
2012-06-27 13:54 ` [PATCH v5 1/9] clocksource: time-armada-370-xp: Marvell Armada 370/XP SoC timer driver Gregory Clement
2012-06-27 13:54 ` [PATCH v5 2/9] arm: mach-mvebu: add header Gregory Clement
2012-06-27 13:54 ` [PATCH v5 3/9] arm: mach-mvebu: add source files Gregory Clement
2012-06-27 15:36   ` Andrew Lunn
2012-06-28 18:07     ` Nicolas Pitre
2012-07-02 11:36     ` Thomas Petazzoni
2012-06-27 13:54 ` [PATCH v5 4/9] arm: mach-mvebu: add support for Armada 370 and Armada XP with DT Gregory Clement
2012-06-27 16:11   ` Ben Dooks
2012-07-02 11:37     ` Thomas Petazzoni
2012-06-27 13:54 ` [PATCH v5 5/9] arm: mach-mvebu: add documentation for new device tree bindings Gregory Clement
2012-06-27 13:54 ` [PATCH v5 6/9] arm: mach-mvebu: add defconfig Gregory Clement
2012-06-27 13:54 ` [PATCH v5 7/9] arm: mach-mvebu: add compilation/configuration change Gregory Clement
2012-06-27 13:54 ` [PATCH v5 8/9] arm: mach-mvebu: add entry to MAINTAINERS Gregory Clement
2012-06-27 13:54 ` [PATCH v5 9/9] ARM: mvebu: MPIC: read number of interrupts from control register Gregory Clement
2012-06-27 15:54 ` Ben Dooks [this message]
2012-07-02  8:30   ` [PATCH v5] arm: Add basic support for new Marvell Armada 370 and Armada XP SoC Thomas Petazzoni
2012-07-02  9:19     ` Ben Dooks
2012-07-02  9:19       ` Thomas Petazzoni
2012-07-02  9:25         ` Ben Dooks
2012-07-02  9:26           ` Thomas Petazzoni
2012-06-27 16:26 ` review comments Ben Dooks
2012-06-27 16:26   ` [PATCH 1/3] arm: mach-mvebu: fixup style error in system-controller Ben Dooks
2012-06-27 16:26   ` [PATCH 2/3] arm: mach-mvebu: check result of of_match_node() Ben Dooks
2012-06-27 16:26   ` [PATCH 3/3] arm: mach-mvebu: system-controller only registers restart if device exists Ben Dooks
2012-06-27 19:19     ` Russell King - ARM Linux
2012-06-28  9:23       ` Ben Dooks
2012-06-28 10:17         ` Russell King - ARM Linux
2012-07-02 11:35   ` review comments Thomas Petazzoni
2012-06-28 12:10 ` [PATCH v5] arm: Add basic support for new Marvell Armada 370 and Armada XP SoC Lior Amsalem

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=4FEB2CC3.7090305@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 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).