All of lore.kernel.org
 help / color / mirror / Atom feed
From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [BUG?] ARM: mvebu: is second PCIe unit of Armada XP mv78230 x1 or x4?
Date: Wed, 6 Nov 2013 15:57:05 +0100	[thread overview]
Message-ID: <20131106155705.444c20b2@skate> (raw)
In-Reply-To: <20131105104845.4fc9e216@skate>

Arnaud,

On Tue, 5 Nov 2013 10:48:45 +0100, Thomas Petazzoni wrote:

> The only place where we (Gregory pointed me in the right direction)
> could find some relation between the SoC variants and the available PCIe
> interfaces is in the hardware manual of each SoC variant, where the
> SERDES lanes are described.
> 
> For MV78230, it says:
> 
> 	PCIe 0.0, 0.1, 0.2, 0.3, 1.0, 1.1 and 1.2

[...]

> What it says for 78230 it a bit weird, because I don't see why it
> mentions 1.1 and 1.2 since the second PCIe interface on 78230 is said
> to be x1. Maybe that's a mistake in the datasheet, I'll try to get a
> confirmation about this.

I've updated the MV78230 hardware datasheet that we had, and indeed the
latest version available has this correct: MV78230 has PCIe 0.0, 0.1,
0.2, 0.3 and 1.0, which means a x4/x1 PCIe interface and a x1 one. The
"1.1" and "1.2" indicated in an earlier version of the datasheet were a
mistake, apparently.

Bottom line: it means that the patch you submitted and that I Acked-by
a few minutes ago is correct.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2013-11-06 14:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-04 18:00 [BUG?] ARM: mvebu: is second PCIe unit of Armada XP mv78230 x1 or x4? Arnaud Ebalard
2013-11-05  8:36 ` Gregory CLEMENT
2013-11-05  9:48 ` Thomas Petazzoni
2013-11-06 14:57   ` Thomas Petazzoni [this message]

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=20131106155705.444c20b2@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 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.