linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: nico@fluxnic.net (Nicolas Pitre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] [RFC] arm: add documentation describing Marvell families of SoC
Date: Tue, 17 Jul 2012 11:45:08 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.02.1207171115161.9293@xanadu.home> (raw)
In-Reply-To: <201207171509.30509.arnd@arndb.de>

On Tue, 17 Jul 2012, Arnd Bergmann wrote:

> On Tuesday 17 July 2012, Thomas Petazzoni wrote:
> > As stated in the introduction of the document, the families of ARM
> > SoCs at Marvell are very complicated, and it is difficult for
> > newcomers to understand the organization of this SoC family and how it
> > relates to the Linux kernel support for those hardware platforms.
> > 
> > This document is only at RFC stage for now, it requires reviews and
> > comments from the Marvell maintainers, the PXA maintainers and the MMP
> > maintainers. For correctness of course, but also to add any other
> > information that would be useful. For example, one of the thing that
> > wasn't clear how to detail in the documentation is how the SoCs relate
> > to each other in terms of hardware IP blocks. For example, most of the
> > Kirkwood/Dove/Armada 370-XP/etc. hardware IPs (I2C, SPI, USB, SATA,
> > etc.) are identical, while the PXA and MMP families are completely
> > separate.
> 
> This is wonderful! Even if there are some pieces missing or incorrect,
> it looks extremely valuable. I remember countless times of browsing
> through the marvell web site and the source code trying to make sense
> of how things fit together.
> 
> Thanks a lot for compiling the list!

Absolutely!

I think I have an old list that was compiled by Lennert.  I'll try to 
dig it out in case this document could benefit from it.

> > +Orion family
> > +------------
> > +
> > +  Flavors:
> > +        88F5082
> > +        88F5181
> > +        88F5181L
> > +        88F5182
> > +        88F5281
> > +        88F6183
> > +  Core: ARMv5 compatible
> > +  Linux kernel directory: arch/arm/mach-orion5x
> > +  No public datasheets available.
> 
> I would also mention that the core in this is "Feroceon", not just that it's ARMv5.
> Same for mv78xx0 and kirkwood.

They're not all Feroceons.  Some of the core names were: Mohawk, 
Jolteon, Flareon, and even Orion might have been a core name initially.  
Possibly others I can't remember now.

> > +        PXA930, PXA935, PXA955
> > +             Core: ARMv5 compatible Sheeva core
> 
> This looks wrong. According to the Kconfig file, PXA93x actually uses the
> same core as PXA3xx, while PXA955 uses an ARMv7 PJ4 core.

Oh, and BTW Flareon is also a PJ4.


Nicolas

  parent reply	other threads:[~2012-07-17 15:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-17 14:26 [PATCH] [RFC] arm: add documentation describing Marvell families of SoC Thomas Petazzoni
2012-07-17 14:59 ` Andrew Lunn
2012-07-17 15:37   ` Thomas Petazzoni
2012-07-17 15:09 ` Arnd Bergmann
2012-07-17 15:40   ` Thomas Petazzoni
2012-07-17 16:52     ` Andrew Lunn
2012-07-17 15:45   ` Nicolas Pitre [this message]
2012-07-17 18:58     ` Nicolas Pitre
2012-08-04 21:01       ` Thomas Petazzoni
2012-07-17 15:35 ` [PATCH v2] " Thomas Petazzoni
2012-07-17 18:01 ` [PATCH] " Eric Miao
2012-07-17 18:05   ` Andrew Lunn
2012-07-17 18:08     ` Eric Miao
2012-07-17 18:35   ` Thomas Petazzoni
2012-07-17 18:50     ` Eric Miao
2012-08-04 20:59   ` 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=alpine.LFD.2.02.1207171115161.9293@xanadu.home \
    --to=nico@fluxnic.net \
    --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).