From: Arnd Bergmann <arnd@arndb.de>
To: Thierry Reding <thierry.reding@avionic-design.de>
Cc: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
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>,
Gregory Clement <gregory.clement@free-electrons.com>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
Olof Johansson <olof@lixom.net>,
Tawfik Bayouk <tawfik@marvell.com>,
Mitch Bradley <wmb@firmworks.com>,
Andrew Murray <andrew.murray@arm.com>
Subject: Re: [PATCHv6 10/17] arm: mvebu: add PCIe Device Tree informations for Armada 370
Date: Tue, 26 Mar 2013 20:50:12 +0000 [thread overview]
Message-ID: <201303262050.12847.arnd@arndb.de> (raw)
In-Reply-To: <20130326201654.GA7109@avionic-0098.mockup.avionic-design.de>
On Tuesday 26 March 2013, Thierry Reding wrote:
> pci@1,0 {
> device_type = "pci";
> assigned-addresses = <0x82000800 0 0x80000000 0 0x1000>;
> reg = <0x000800 0 0 0 0>;
> status = "disabled";
>
> #address-cells = <3>;
> #size-cells = <2>;
>
> nvidia,num-lanes = <2>;
> };
Shouldn't there be an empty ranges property in there as well?
Arnd
next prev parent reply other threads:[~2013-03-26 20:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 16:18 [PATCHv6 00/17] PCIe support for the Armada 370 and Armada XP SoCs Thomas Petazzoni
2013-03-26 16:18 ` [PATCHv6 01/17] of/pci: Provide support for parsing PCI DT ranges property Thomas Petazzoni
2013-03-26 16:18 ` [PATCHv6 02/17] of/pci: Add of_pci_get_devfn() function Thomas Petazzoni
2013-03-26 16:18 ` [PATCHv6 03/17] of/pci: Add of_pci_parse_bus_range() function Thomas Petazzoni
2013-03-26 16:18 ` [PATCHv6 04/17] pci: infrastructure to add drivers in drivers/pci/host Thomas Petazzoni
2013-03-26 16:18 ` [PATCHv6 05/17] arm: pci: add a align_resource hook Thomas Petazzoni
2013-03-26 16:18 ` [PATCHv6 06/17] clk: mvebu: create parent-child relation for PCIe clocks on Armada 370 Thomas Petazzoni
2013-03-26 16:18 ` [PATCHv6 07/17] clk: mvebu: add more PCIe clocks for Armada XP Thomas Petazzoni
2013-03-26 16:18 ` [PATCHv6 08/17] pci: PCIe driver for Marvell Armada 370/XP systems Thomas Petazzoni
2013-03-26 16:18 ` [PATCHv6 09/17] arm: mvebu: PCIe support is now available on mvebu Thomas Petazzoni
2013-03-26 16:18 ` [PATCHv6 10/17] arm: mvebu: add PCIe Device Tree informations for Armada 370 Thomas Petazzoni
2013-03-26 16:34 ` Jason Gunthorpe
2013-03-26 16:58 ` Thomas Petazzoni
[not found] ` <20130326163421.GA30255-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2013-03-26 20:16 ` Thierry Reding
2013-03-26 20:50 ` Arnd Bergmann [this message]
[not found] ` <201303262050.12847.arnd-r2nGTMty4D4@public.gmane.org>
2013-03-26 21:12 ` Thierry Reding
2013-03-26 21:17 ` Arnd Bergmann
2013-03-26 21:27 ` Thomas Petazzoni
2013-03-26 22:51 ` Jason Gunthorpe
2013-03-27 6:36 ` Thierry Reding
2013-03-26 16:18 ` [PATCHv6 11/17] arm: mvebu: add PCIe Device Tree informations for Armada XP Thomas Petazzoni
2013-03-26 16:18 ` [PATCHv6 12/17] arm: mvebu: PCIe Device Tree informations for OpenBlocks AX3-4 Thomas Petazzoni
2013-03-26 16:18 ` [PATCHv6 13/17] arm: mvebu: PCIe Device Tree informations for Armada XP DB Thomas Petazzoni
2013-03-26 16:18 ` [PATCHv6 14/17] arm: mvebu: PCIe Device Tree informations for Armada 370 Mirabox Thomas Petazzoni
2013-03-26 16:18 ` [PATCHv6 15/17] arm: mvebu: PCIe Device Tree informations for Armada 370 DB Thomas Petazzoni
2013-03-26 16:18 ` [PATCHv6 16/17] arm: mvebu: PCIe Device Tree informations for Armada XP GP Thomas Petazzoni
2013-03-26 16:18 ` [PATCHv6 17/17] arm: mvebu: update defconfig with PCI and USB support Thomas Petazzoni
2013-03-26 16:32 ` [PATCHv6 00/17] PCIe support for the Armada 370 and Armada XP SoCs Arnd Bergmann
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=201303262050.12847.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 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).