From: Mason <slash.tmp@free.fr>
To: David Laight <david.laight@aculab.com>,
linux-pci <linux-pci@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Arnd Bergmann <arnd@arndb.de>, Rob Herring <robh@kernel.org>,
Phuong Nguyen <phuong_nguyen@sigmadesigns.com>,
Thibaud Cornic <thibaud_cornic@sigmadesigns.com>,
Marc Zyngier <marc.zyngier@arm.com>,
Shawn Lin <shawn.lin@rock-chips.com>,
Bjorn Helgaas <helgaas@kernel.org>
Subject: Re: Neophyte questions about PCIe
Date: Wed, 8 Mar 2017 15:17:51 +0100 [thread overview]
Message-ID: <b735b894-4c6c-5eb0-524e-dccee648d0f8@free.fr> (raw)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6DCFE7A70A@AcuExch.aculab.com>
Hello David,
On 08/03/2017 14:54, David Laight wrote:
> Mason wrote:
>
>> 2) On my platform, there are two revisions of the PCIe controller.
>> Rev1 muxes config and mem inside a 256 MB window, and doesn't support
>> I/O space.
>> Rev2 muxes all 3 spaces inside a 256 MB window.
>
> Don't think config space fits.
> With the 'obvious' mapping the 'bus number' is in the top
> 8 bits of the address.
https://www.kernel.org/doc/Documentation/devicetree/bindings/pci/host-generic-pci.txt
cfg_offset(bus, device, function, register) =
bus << 20 | device << 15 | function << 12 | register
8 bits for bus, 5 bits for device, 3 bits for function, 12 bits for reg offset
1 MB per bus, 256 buses max => 256 MB max
Supporting "only" 64 buses is good enough, I believe.
>> 3) What happens if a device requires more than 256 MB of
>> mem space? (Is that common? What kind of device? GPUs?)
>> Our controller supports a remapping "facility" to add an
>> offset to the bus address. Is such a feature supported
>> by Linux at all? The problem is that this creates
>> another race condition, as setting the offset register
>> before an access may occur concurrently on two cores.
>> Perhaps 256 MB is plenty on a 32-bit embedded device?
>
> GPUs tend to have their own paging scheme.
> So don't need humongous windows.
> I'm not sure how much space is really needed.
> 32bit x86 reserve the top 1GB of physical address for PCI(e).
I'm hoping 128 MB mem is enough. The two cards I have that are correctly
detected request 8 KB. (I have other cards that are not enumerated at all...
No idea why at the moment.)
>> 4) The HW dev is considering the following fix.
>> Instead of muxing the address spaces, provide smaller
>> exclusive spaces. For example
>> [0x5000_0000, 0x5400_0000] for config (64MB)
>> [0x5400_0000, 0x5800_0000] for I/O (64MB)
>> [0x5800_0000, 0x6000_0000] for mem (128MB)
>
> You almost certainly don't need more than 64k of IO.
Good to know.
> Config space isn't dense, you (probably) need 25 bits to get a 2nd bus number.
> Even 256MB constrains you to 16 bus numbers.
Unless I got the math wrong, it's 20 bits (1 MB) per bus.
So 64 MB allows 64 buses.
> Is this an ARM cpu inside an altera (now intel) fpga??
> There is a nasty bug in their PCIe to avalon bridge logic (fixed in quartus 16.1).
The PCIe controller is from PLDA, and it's embedded in a SoC
where the CPU is a multi-core ARM Cortex A9 MP.
Regards.
next prev parent reply other threads:[~2017-03-08 14:17 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 22:45 Neophyte questions about PCIe Mason
2017-03-08 13:39 ` Mason
2017-03-08 13:54 ` David Laight
2017-03-08 14:17 ` Mason [this message]
2017-03-08 14:38 ` David Laight
2017-03-09 22:01 ` Jeremy Linton
2017-03-08 15:17 ` Bjorn Helgaas
2017-03-09 23:43 ` Mason
2017-03-10 13:15 ` Robin Murphy
2017-03-10 14:06 ` David Laight
2017-03-10 15:05 ` Mason
2017-03-10 15:14 ` David Laight
2017-03-10 15:33 ` Mason
2017-03-10 15:23 ` Robin Murphy
2017-03-10 15:35 ` David Laight
2017-03-10 16:00 ` Robin Murphy
2017-03-13 10:59 ` Mason
2017-03-13 11:56 ` Robin Murphy
2017-03-10 18:49 ` Bjorn Helgaas
2017-03-10 14:53 ` Mason
2017-03-10 16:45 ` Mason
2017-03-10 17:49 ` Mason
2017-03-11 10:57 ` Mason
2017-03-13 21:40 ` Bjorn Helgaas
2017-03-13 21:57 ` Mason
2017-03-13 22:46 ` Bjorn Helgaas
2017-03-14 10:23 ` David Laight
2017-03-14 12:05 ` Mason
2017-03-14 12:24 ` David Laight
2017-03-13 14:25 ` Mason
2017-03-14 14:00 ` Mason
2017-03-14 15:54 ` Mason
2017-03-14 21:46 ` Bjorn Helgaas
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=b735b894-4c6c-5eb0-524e-dccee648d0f8@free.fr \
--to=slash.tmp@free.fr \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=david.laight@aculab.com \
--cc=helgaas@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=phuong_nguyen@sigmadesigns.com \
--cc=robh@kernel.org \
--cc=shawn.lin@rock-chips.com \
--cc=thibaud_cornic@sigmadesigns.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).