linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lian Minghuan-B31939 <B31939@freescale.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Scott Wood <scottwood@freescale.com>,
	Minghuan Lian <Minghuan.Lian@freescale.com>,
	<linux-pci@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	Zang Roy-R61911 <r61911@freescale.com>,
	Hu Mingkai-B21284 <B21284@freescale.com>,
	"Yoder Stuart-B08248" <stuart.yoder@freescale.com>,
	Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH v2 3/3] PCI: Layerscape: Add Layerscape PCIe driver
Date: Wed, 17 Sep 2014 10:26:43 +0000	[thread overview]
Message-ID: <541961E3.909@freescale.com> (raw)
In-Reply-To: <201409161833.53176.arnd@arndb.de>

Hi Arnd,

On 2014年09月16日 16:33, Arnd Bergmann wrote:
> On Tuesday 16 September 2014, Lian Minghuan-B31939 wrote:
>>>>>> +          ranges = <0x81000000 0x0 0x00000000 0x40 0x10000000 0x0 0x00010000   /* downstream I/O */
>>>>>> +                    0x82000000 0x0 0x00000000 0x41 0x00000000 0x1 0x00000000>; /* non-prefetchable memory */
>>>>> Are these ranges hardcoded in the SoC, or are they the result of iATU
>>>>> settings?  If the latter, who configures it and why no prefetchable
>>>>> region?
>>>> [Minghuan] 400000_0000 - 480000_0000 is hardcode assigned to PEX1.
>>>> I separates from this 32 region  1M for IO, 4G for non-prefetchable memory.
>>>> 4G is the max size iATU supported.
>>>> IO and memory region will be set to iATU by pci-designware.c
>>>> Because both powerpc and imx do not set prefechable memory,
>>>> so  I do not assign prefetchable memory either.
>>> If there's spare room in the addres space for a prefetchable region, why
>>> not make one, regardless of what PPC and IMX do?
>>>
>>> FWIW, I believe that ARMv8 can make better use of a prefetchable region
>>> due to the "gathering" storage attribute, so even if you don't use one
>>> on LS1021A consider using one on ARMv8-based LS chips.
>> [Minghuan] Ok, I will add 4G prefetchable memory region.
> I guess that means you still can't support devices that require 64-bit
> BARs, right? 4GB may be too small for some devices.
>
> Do I read this right that you could have multiple adjacent 4GB areas
> but are limited on registers to set up these areas?
[Minghuan] Yes, an iATU supports up to 4GB in size. We can create 
multiple iATU
to cover a region larger than 4G.
> 	Arnd


      reply	other threads:[~2014-09-17  2:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-11 21:08 [PATCH v2 1/3] PCI: designware: Rename get_msi_data to get_msi_addr Minghuan Lian
2014-09-11 21:09 ` [PATCH v2 2/3] PCI: designware: Add get_msi_data to pcie_host_ops Minghuan Lian
2014-09-11 21:09 ` [PATCH v2 3/3] PCI: Layerscape: Add Layerscape PCIe driver Minghuan Lian
2014-09-11 21:24   ` Scott Wood
2014-09-12 11:10     ` Lian Minghuan-B31939
2014-09-16  4:19       ` Scott Wood
2014-09-16 17:38         ` Lian Minghuan-B31939
2014-09-16 16:33           ` Arnd Bergmann
2014-09-17 10:26             ` Lian Minghuan-B31939 [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=541961E3.909@freescale.com \
    --to=b31939@freescale.com \
    --cc=B21284@freescale.com \
    --cc=Minghuan.Lian@freescale.com \
    --cc=arnd@arndb.de \
    --cc=bhelgaas@google.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=r61911@freescale.com \
    --cc=scottwood@freescale.com \
    --cc=stuart.yoder@freescale.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).