From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC v1 0/5] ARM: Initial support for Marvell Armada 1500
Date: Tue, 27 Aug 2013 18:51:29 +0200 [thread overview]
Message-ID: <20130827185129.31bd0c9e@skate> (raw)
In-Reply-To: <521CD7B9.7060208@gmail.com>
Dear Sebastian Hesselbarth,
On Tue, 27 Aug 2013 18:45:45 +0200, Sebastian Hesselbarth wrote:
> > After talking a bit with engineers within Marvell that work on this
> > SoC, I'm inclined to think that using mach-mvebu for this family of SoC
> > is not a good idea.
>
> Thomas,
>
> thanks for the info below. Reading a little bit through the GPL'ed
> source, I also quickly came to the same conclusion. It is more likely
> we can reuse some stuff from other SoCs than Orion or Armada 370/XP.
Yes, many of the IP blocks are for example DesignWare IPs, or ARM IPs
in the case of the Cortex-A based variants.
> > The codename used for those Armada 1500 SOCs is "Berlin", so a name
> > like mach-berlin, or mach-mvberlin (if we want to keep 'mv' to identify
> > the founder) seems like a good name.
>
> I have already moved it under mach-mv88de3xxx as for now, all SoCs
> Marvell is providing as DE (Digital Entertainment) fit in that. I like
> mach-codename style more than plain numbers, maybe I rename the folder
> to mach-berlin before posting.
I also like mach-berlin a bit more than mach-mve88de3xxx, for a very
silly reason: when during a discussion you have to say mach-mv88de3xxx,
it's pretty annoying. We already have the horrible mach-mv78xx0, let's
not add more of this :)
> Speaking of "berlin", they found a 2WW bomb in my home town center today
> and are evacuating apartments. Mine too, so it looks like I'll have
> some time to prepare v2 tonight..
Doh!
> > Also, to help us understand the organization of the family of SOCs, I
> > asked a few informations to Marvell, and here is what I could collect:
> >
> > """
> > BGxname CPU core codename L2 cache controller internal name
> > BG2 PJ4B Armada1500 Tauros3 MV88DE3100
> > BG2-CT Cortex-A9 N/A PL310 N/A
> > BG3 Cortex-A15 N/A CA15 integrated N/A
> > """
> >
> > As was told that the Armada X or MV88DEx names are not used during
> > development, and what Marvell is really using are the BGxx names.
>
> Ok, I'll add that info to Marvell SoC documentation also.
That'd be nice indeed.
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-08-27 16:51 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 19:41 [RFC v1 0/5] ARM: Initial support for Marvell Armada 1500 Sebastian Hesselbarth
[not found] ` <1376682098-10580-5-git-send-email-sebastian.hesselbarth@gmail.com>
2013-08-16 19:50 ` [RFC v1 4/5] ARM: mvebu: add Armada 1500 and Sony NSZ-GS7 device tree files Jason Cooper
2013-08-16 19:54 ` Sebastian Hesselbarth
2013-08-16 20:22 ` Jason Cooper
2013-08-17 19:28 ` Arnd Bergmann
2013-08-18 23:11 ` Sebastian Hesselbarth
2013-08-19 8:46 ` Arnd Bergmann
[not found] ` <1376682098-10580-2-git-send-email-sebastian.hesselbarth@gmail.com>
2013-08-17 13:24 ` [RFC v1 1/5] irqchip: add Armada 1500 APB interrupt controller Sebastian Hesselbarth
[not found] ` <1376682098-10580-4-git-send-email-sebastian.hesselbarth@gmail.com>
2013-08-16 20:39 ` [RFC v1 3/5] ARM: mvebu: add Armada 150 uart to lowlevel debug Jason Cooper
2013-08-17 19:01 ` Arnd Bergmann
[not found] ` <1376682098-10580-6-git-send-email-sebastian.hesselbarth@gmail.com>
2013-08-16 20:48 ` [RFC v1 5/5] ARM: mvebu: add board init for Armada 1500 Jason Cooper
2013-08-17 13:01 ` Sebastian Hesselbarth
2013-08-17 19:08 ` Arnd Bergmann
2013-08-17 19:13 ` Arnd Bergmann
2013-08-18 23:01 ` Sebastian Hesselbarth
2013-08-19 7:44 ` Arnd Bergmann
2013-08-19 14:52 ` Sebastian Hesselbarth
2013-08-19 17:47 ` Arnd Bergmann
2013-08-17 15:38 ` Thomas Petazzoni
2013-08-17 19:12 ` Arnd Bergmann
2013-08-18 23:02 ` Sebastian Hesselbarth
2013-08-19 7:58 ` Arnd Bergmann
2013-08-17 19:32 ` [RFC v1 0/5] ARM: Initial support for Marvell " Arnd Bergmann
2013-08-18 23:21 ` Sebastian Hesselbarth
2013-08-19 8:03 ` Arnd Bergmann
2013-08-18 16:34 ` Thomas Petazzoni
2013-08-27 14:19 ` Thomas Petazzoni
2013-08-27 16:45 ` Sebastian Hesselbarth
2013-08-27 16:51 ` Thomas Petazzoni [this message]
2013-08-27 19:38 ` Arnd Bergmann
2013-08-28 0:14 ` [PATCH RFC v2 0/6] " Sebastian Hesselbarth
2013-08-28 0:14 ` [PATCH RFC v2 1/6] irqchip: add DesignWare APB ICTL interrupt controller Sebastian Hesselbarth
2013-08-28 0:14 ` [PATCH RFC v2 2/6] ARM: add Marvell Berlin SoC familiy to Marvell doc Sebastian Hesselbarth
2013-08-28 0:14 ` [PATCH RFC v2 3/6] ARM: add Marvell Berlin and Armada 1500 to multi_v7_defconfig Sebastian Hesselbarth
2013-08-28 0:14 ` [PATCH RFC v2 4/6] ARM: add Marvell Berlin UART0 lowlevel debug Sebastian Hesselbarth
2013-08-28 0:14 ` [PATCH RFC v2 5/6] ARM: add Armada 1500 and Sony NSZ-GS7 device tree files Sebastian Hesselbarth
2013-08-28 12:14 ` Jason Cooper
2013-08-28 12:23 ` Sebastian Hesselbarth
2013-08-28 0:14 ` [PATCH RFC v2 6/6] ARM: add initial support for Marvell Berlin SoCs Sebastian Hesselbarth
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=20130827185129.31bd0c9e@skate \
--to=thomas.petazzoni@free-electrons.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).