All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robherring2@gmail.com>
To: monstr@monstr.eu
Cc: devicetree-discuss@lists.ozlabs.org,
	Grant Likely <grant.likely@secretlab.ca>,
	linux-pci@vger.kernel.org, Rob Herring <rob.herring@calxeda.com>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: pci and pcie device-tree binding - range No cells
Date: Mon, 10 Dec 2012 08:26:37 -0600	[thread overview]
Message-ID: <50C5F11D.9060006@gmail.com> (raw)
In-Reply-To: <50C5D387.90908@monstr.eu>

On 12/10/2012 06:20 AM, Michal Simek wrote:
> Hi Grant and others,
> 
> I have a question regarding number of cells in ranges property
> for pci and pcie nodes.
> 
> Linux pci/pcie powerpc DTSes contain 7 cells (xpedite5370.dts,
> sequoia.dts, etc)
> but also 6 cells format too (mpc832x_mds.dts)
> 
> Here is shown 6 cells ranges format and describe
> http://devicetree.org/Device_Tree_Usage#PCI_Host_Bridge
> 
> And also in documentation in the linux
> Documentation/devicetree/bindings/pci/83xx-512x-pci.txt
> 
> Both format uses:
> #size-cells = <2>;
> #address-cells = <3>;
> 
> What is valid format?

Both. 7 cells are valid when the host (parent) bus is 64-bit and 6 cells
are valid when the host bus is 32-bit. The ranges property is <<child
address> <parent address> <size>>. The parent address #address-cells is
taken from the parent node.

Rob

WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robherring2@gmail.com>
To: monstr@monstr.eu
Cc: linux-pci@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
	Rob Herring <rob.herring@calxeda.com>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: pci and pcie device-tree binding - range No cells
Date: Mon, 10 Dec 2012 08:26:37 -0600	[thread overview]
Message-ID: <50C5F11D.9060006@gmail.com> (raw)
In-Reply-To: <50C5D387.90908@monstr.eu>

On 12/10/2012 06:20 AM, Michal Simek wrote:
> Hi Grant and others,
> 
> I have a question regarding number of cells in ranges property
> for pci and pcie nodes.
> 
> Linux pci/pcie powerpc DTSes contain 7 cells (xpedite5370.dts,
> sequoia.dts, etc)
> but also 6 cells format too (mpc832x_mds.dts)
> 
> Here is shown 6 cells ranges format and describe
> http://devicetree.org/Device_Tree_Usage#PCI_Host_Bridge
> 
> And also in documentation in the linux
> Documentation/devicetree/bindings/pci/83xx-512x-pci.txt
> 
> Both format uses:
> #size-cells = <2>;
> #address-cells = <3>;
> 
> What is valid format?

Both. 7 cells are valid when the host (parent) bus is 64-bit and 6 cells
are valid when the host bus is 32-bit. The ranges property is <<child
address> <parent address> <size>>. The parent address #address-cells is
taken from the parent node.

Rob

  reply	other threads:[~2012-12-10 14:26 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-10 12:20 pci and pcie device-tree binding - range No cells Michal Simek
2012-12-10 14:26 ` Rob Herring [this message]
2012-12-10 14:26   ` Rob Herring
2012-12-10 15:05   ` Michal Simek
2012-12-10 15:05     ` Michal Simek
2012-12-10 15:21     ` Rob Herring
2012-12-10 15:21       ` Rob Herring
2012-12-10 15:37       ` Michal Simek
2012-12-10 15:37         ` Michal Simek
2012-12-10 15:52         ` David Laight
2012-12-10 15:52           ` David Laight
2012-12-10 15:52           ` David Laight
2012-12-10 16:05           ` Michal Simek
2012-12-10 16:05             ` Michal Simek
2012-12-10 17:15             ` Thomas Petazzoni
2012-12-10 17:15               ` Thomas Petazzoni
2012-12-10 23:24               ` Rob Herring
2012-12-10 23:24                 ` Rob Herring
2012-12-12 16:16                 ` Thomas Petazzoni
2012-12-12 16:16                   ` Thomas Petazzoni
2012-12-12 17:22                   ` Grant Likely
2012-12-12 17:22                     ` Grant Likely
2012-12-12 17:29                   ` Rob Herring
2012-12-12 17:29                     ` Rob Herring
2012-12-10 16:02         ` Rob Herring
2012-12-10 16:02           ` Rob Herring
2012-12-10 16:11           ` Michal Simek
2012-12-10 16:11             ` Michal Simek
2012-12-10 21:43         ` Grant Likely
2012-12-10 21:43           ` Grant Likely
2012-12-10 22:38           ` Benjamin Herrenschmidt
2012-12-10 22:38             ` Benjamin Herrenschmidt
2012-12-10 23:11             ` Mitch Bradley
2012-12-10 23:11               ` Mitch Bradley
2012-12-10 23:11               ` Mitch Bradley
2012-12-10 21:41       ` Grant Likely
2012-12-10 21:41         ` Grant Likely
2012-12-12 10:37         ` Michal Simek
2012-12-12 10:37           ` Michal Simek
2012-12-12 10:49           ` Grant Likely
2012-12-12 10:49             ` Grant Likely
     [not found]             ` <CAPcvp5EJH-Q6wd7my+V+FUVE1=hzwMN-yOfHiukGvDmkcoRcsQ@mail.gmail.com>
2012-12-12 12:19               ` Andrew Murray
2012-12-12 12:19                 ` Andrew Murray
2012-12-12 13:34                 ` Thierry Reding
2012-12-12 13:34                   ` Thierry Reding
2012-12-12 16:44                   ` Andrew Murray
2012-12-12 16:44                     ` Andrew Murray
2012-12-12 16:55             ` Michal Simek
2012-12-12 16:55               ` Michal Simek

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=50C5F11D.9060006@gmail.com \
    --to=robherring2@gmail.com \
    --cc=benh@kernel.crashing.org \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-pci@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=monstr@monstr.eu \
    --cc=rob.herring@calxeda.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.