From: Arnd Bergmann <arnd@arndb.de>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Grant Likely <grant.likely@secretlab.ca>,
Russell King <linux@arm.linux.org.uk>,
linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree-discuss@lists.ozlabs.org,
Lior Amsalem <alior@marvell.com>, Andrew Lunn <andrew@lunn.ch>,
Jason Cooper <jason@lakedaemon.net>,
Maen Suleiman <maen@marvell.com>,
Thierry Reding <thierry.reding@avionic-design.de>,
Gregory Clement <gregory.clement@free-electrons.com>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
Olof Johansson <olof@lixom.net>,
Tawfik Bayouk <tawfik@marvell.com>,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
Mitch Bradley <wmb@firmworks.com>,
Andrew Murray <andrew.murray@arm.com>
Subject: Re: [RFC PATCHv1 0/5] Use the mvebu PCIe driver on Kirkwood
Date: Wed, 27 Mar 2013 18:07:50 +0000 [thread overview]
Message-ID: <201303271807.51023.arnd@arndb.de> (raw)
In-Reply-To: <1364407504-13524-1-git-send-email-thomas.petazzoni@free-electrons.com>
On Wednesday 27 March 2013, Thomas Petazzoni wrote:
> Here is a set of five patches that demonstrate that the mvebu PCIe
> driver can be used on Kirkwood with no modification at all. Those
> patches are not meant to be applied yet, the Device Trees are not
> completely correct yet (they don't take into account the fact that
> 6281 has one PCIe interface and 6282 has two PCIe interface).
>
> It took less than two hours to enable PCIe on Kirkwood (and in those
> two hours, the conversion of the DB-88F6281 board to the Device Tree
> has been done as well), and the result works fine:
>
> # /usr/sbin/lspci
> 00:01.0 PCI bridge: Marvell Technology Group Ltd. Device 7846
> 00:02.0 PCI bridge: Marvell Technology Group Ltd. Device 7846
> 01:00.0 SCSI storage controller: Marvell Technology Group Ltd. 88SX7042 PCI-e 4-port SATA-II (rev 02)
> 02:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) (rev 06)
>
> # cat /proc/cpuinfo | grep ^Hardware
> Hardware : Marvell Kirkwood (Flattened Device Tree)
Very nice!
> I've tested both the e1000e NIC card and the SATA 4 ports card and
> they work fine.
I assume it works with PIO, but does the SATA card use the I/O
space registers, or just memory space?
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCHv1 0/5] Use the mvebu PCIe driver on Kirkwood
Date: Wed, 27 Mar 2013 18:07:50 +0000 [thread overview]
Message-ID: <201303271807.51023.arnd@arndb.de> (raw)
In-Reply-To: <1364407504-13524-1-git-send-email-thomas.petazzoni@free-electrons.com>
On Wednesday 27 March 2013, Thomas Petazzoni wrote:
> Here is a set of five patches that demonstrate that the mvebu PCIe
> driver can be used on Kirkwood with no modification at all. Those
> patches are not meant to be applied yet, the Device Trees are not
> completely correct yet (they don't take into account the fact that
> 6281 has one PCIe interface and 6282 has two PCIe interface).
>
> It took less than two hours to enable PCIe on Kirkwood (and in those
> two hours, the conversion of the DB-88F6281 board to the Device Tree
> has been done as well), and the result works fine:
>
> # /usr/sbin/lspci
> 00:01.0 PCI bridge: Marvell Technology Group Ltd. Device 7846
> 00:02.0 PCI bridge: Marvell Technology Group Ltd. Device 7846
> 01:00.0 SCSI storage controller: Marvell Technology Group Ltd. 88SX7042 PCI-e 4-port SATA-II (rev 02)
> 02:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) (rev 06)
>
> # cat /proc/cpuinfo | grep ^Hardware
> Hardware : Marvell Kirkwood (Flattened Device Tree)
Very nice!
> I've tested both the e1000e NIC card and the SATA 4 ports card and
> they work fine.
I assume it works with PIO, but does the SATA card use the I/O
space registers, or just memory space?
Arnd
next prev parent reply other threads:[~2013-03-27 18:08 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 18:04 [RFC PATCHv1 0/5] Use the mvebu PCIe driver on Kirkwood Thomas Petazzoni
2013-03-27 18:04 ` Thomas Petazzoni
2013-03-27 18:05 ` [RFC PATCHv1 1/5] pci: mvebu: enable driver usage " Thomas Petazzoni
2013-03-27 18:05 ` Thomas Petazzoni
2013-03-27 18:05 ` [RFC PATCHv1 2/5] bus: mvebu: fix mistake in PCIe window target attribute for Kirkwood Thomas Petazzoni
2013-03-27 18:05 ` Thomas Petazzoni
2013-04-03 10:52 ` Thomas Petazzoni
2013-04-03 10:52 ` Thomas Petazzoni
2013-04-03 10:57 ` Jason Cooper
2013-04-03 10:57 ` Jason Cooper
2013-04-03 11:05 ` Thomas Petazzoni
2013-04-03 11:05 ` Thomas Petazzoni
2013-03-27 18:05 ` [RFC PATCHv1 3/5] arm: mach-kirkwood: seperate PCIe window init from other windows Thomas Petazzoni
2013-03-27 18:05 ` Thomas Petazzoni
2013-03-27 18:35 ` Jason Gunthorpe
2013-03-27 18:35 ` Jason Gunthorpe
2013-03-27 20:17 ` Thomas Petazzoni
2013-03-27 20:17 ` Thomas Petazzoni
2013-03-27 18:05 ` [RFC PATCHv1 4/5] arm: kirkwood: add SoC-level Device Tree data for PCIe interfaces Thomas Petazzoni
2013-03-27 18:05 ` Thomas Petazzoni
2013-03-27 18:05 ` [RFC PATCHv1 5/5] arm: kirkwood: convert db-88f6281 to the Device Tree Thomas Petazzoni
2013-03-27 18:05 ` Thomas Petazzoni
2013-03-27 18:07 ` Arnd Bergmann [this message]
2013-03-27 18:07 ` [RFC PATCHv1 0/5] Use the mvebu PCIe driver on Kirkwood Arnd Bergmann
2013-03-27 18:11 ` Thomas Petazzoni
2013-03-27 18:11 ` Thomas Petazzoni
2013-03-27 18:18 ` Thomas Petazzoni
2013-03-27 18:18 ` 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=201303271807.51023.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=alior@marvell.com \
--cc=andrew.murray@arm.com \
--cc=andrew@lunn.ch \
--cc=bhelgaas@google.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=ezequiel.garcia@free-electrons.com \
--cc=grant.likely@secretlab.ca \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=maen@marvell.com \
--cc=olof@lixom.net \
--cc=tawfik@marvell.com \
--cc=thierry.reding@avionic-design.de \
--cc=thomas.petazzoni@free-electrons.com \
--cc=wmb@firmworks.com \
/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.