All of lore.kernel.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 02/10] ARM: mvebu: add initial support for the Armada 375 SOCs
Date: Wed, 12 Feb 2014 14:08:42 +0100	[thread overview]
Message-ID: <3797172.YJcGPMeT5Y@wuerfel> (raw)
In-Reply-To: <1392200619-3141-3-git-send-email-thomas.petazzoni@free-electrons.com>

On Wednesday 12 February 2014 11:23:31 Thomas Petazzoni wrote:
> From: Gregory CLEMENT <gregory.clement@free-electrons.com>
> 
> This commit adds the basic support for the Armada 375 SOCs. These SoCs
> share most of their IP with the Armada 370/XP SoCs. The main
> difference is the use of a Cortex A9 CPU instead of the PJ4B CPU. The
> interrupt controller and the L2 cache controller are also different
> they are respectively the GIC and the PL310.
> 
> Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
>  .../devicetree/bindings/arm/armada-375.txt         |  9 +++++
>  arch/arm/mach-mvebu/Kconfig                        | 15 ++++++++
>  arch/arm/mach-mvebu/Makefile                       |  1 +
>  arch/arm/mach-mvebu/armada-375.c                   | 44 ++++++++++++++++++++++

I don't know what the outcome was for the first version, but just
for the record, I would prefer merging the board file into armada-370-xp.c
without renaming that file. Keeping the separate Kconfig entry makes sense
because we want to select different options there. If you have differences
between the implementations (so far the 370/xp code should just work
on 375), you can use a combination of if(IS_ENABLED(CONFIG_*)) and
if(machine_is_compatible()) to do the detection but keep a common
dt_compat list.

	Arnd

  reply	other threads:[~2014-02-12 13:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-12 10:23 [PATCH v2 00/10] Core support for Marvell Armada 375 and 38x Thomas Petazzoni
2014-02-12 10:23 ` [PATCH v2 01/10] ARM: mvebu: add Armada 375 support to the system-controller driver Thomas Petazzoni
2014-02-12 10:23 ` [PATCH v2 02/10] ARM: mvebu: add initial support for the Armada 375 SOCs Thomas Petazzoni
2014-02-12 13:08   ` Arnd Bergmann [this message]
2014-02-13 10:55     ` Thomas Petazzoni
2014-02-12 10:23 ` [PATCH v2 03/10] ARM: mvebu: add workaround for data abort issue on Armada 375 Thomas Petazzoni
2014-02-12 13:10   ` Arnd Bergmann
2014-02-13 10:56     ` Thomas Petazzoni
2014-02-12 10:23 ` [PATCH v2 04/10] ARM: mvebu: add Device Tree description of the Armada 375 SoC Thomas Petazzoni
2014-02-12 10:23 ` [PATCH v2 05/10] ARM: mvebu: add Device Tree for the Armada 375 DB board Thomas Petazzoni
2014-02-12 13:12   ` Arnd Bergmann
2014-02-13 10:56     ` Thomas Petazzoni
2014-02-12 10:23 ` [PATCH v2 06/10] ARM: mvebu: add initial support for the Armada 380/385 SOCs Thomas Petazzoni
2014-02-12 10:23 ` [PATCH v2 07/10] ARM: mvebu: add Device Tree description of the Armada 380/385 SoCs Thomas Petazzoni
2014-02-12 10:23 ` [PATCH v2 08/10] ARM: mvebu: add Device Tree for the Armada 385 DB board Thomas Petazzoni
2014-02-12 10:23 ` [PATCH v2 09/10] ARM: mvebu: update defconfigs for Armada 375 and 38x Thomas Petazzoni
2014-02-12 10:23 ` [PATCH v2 10/10] Documentation: arm: update Marvell documentation about Armada 375/38x Thomas Petazzoni

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=3797172.YJcGPMeT5Y@wuerfel \
    --to=arnd@arndb.de \
    --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.