From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 6/9] ARM: shmobile: Add PCIe device tree nodes for R8A7790
Date: Tue, 25 Mar 2014 19:42:42 +0100 [thread overview]
Message-ID: <14997425.EPjrKhVy10@wuerfel> (raw)
In-Reply-To: <1395766604-30926-7-git-send-email-phil.edworthy@renesas.com>
On Tuesday 25 March 2014 16:56:41 Phil Edworthy wrote:
> + /* Map all possible DDR as inbound ranges */
> + dma-ranges = <0x42000000 0 0x40000000 0 0x40000000 0 0x80000000
> + 0x43000000 1 0x80000000 1 0x80000000 0 0x80000000>;
Typo: 0x43000000 should be 0x42000000 I guess.
Since you control the mapping, I wonder if you could also do this as
dma-ranges = <0x42000000 0 0x00000000 0 0x40000000 0 0x80000000
0x43000000 0 0x80000000 1 0x80000000 0 0x80000000>;
i.e. map all the RAM into PCI bus addresses below the 32-bit boundary.
This would be really nice from the perspective that now all PCI
devices could access all of RAM without using an IOMMU or the
relying on 64-bit master capability.
The downside of this is that you'd probably need a custom dma_map_ops
wrapper.
Arnd
next prev parent reply other threads:[~2014-03-25 18:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 16:56 [PATCH v5 0/9] R-Car Gen2 PCIe host driver Phil Edworthy
2014-03-25 16:56 ` [PATCH v5 1/9] PCI: host: rcar: Add Renesas R-Car PCIe driver Phil Edworthy
2014-03-25 16:56 ` [PATCH v5 2/9] PCI: host: rcar: Add MSI support Phil Edworthy
2014-03-25 17:04 ` Ben Dooks
2014-03-26 10:12 ` Phil.Edworthy at renesas.com
2014-03-25 16:56 ` [PATCH v5 3/9] ARM: shmobile: r8a7790: Add PCIe clock device tree nodes Phil Edworthy
2014-03-25 16:56 ` [PATCH v5 4/9] ARM: shmobile: r8a7791: " Phil Edworthy
2014-03-25 16:56 ` [PATCH v5 5/9] dt-bindings: pci: rcar pcie device tree bindings Phil Edworthy
2014-03-25 20:22 ` Sergei Shtylyov
2014-03-26 9:12 ` Phil.Edworthy at renesas.com
2014-03-25 16:56 ` [PATCH v5 6/9] ARM: shmobile: Add PCIe device tree nodes for R8A7790 Phil Edworthy
2014-03-25 18:42 ` Arnd Bergmann [this message]
2014-03-26 9:55 ` Phil.Edworthy at renesas.com
2014-03-26 10:34 ` Arnd Bergmann
2014-03-26 11:01 ` Phil.Edworthy at renesas.com
2014-03-26 11:14 ` Arnd Bergmann
2014-03-26 11:34 ` Phil.Edworthy at renesas.com
2014-03-26 11:52 ` Arnd Bergmann
2014-03-26 11:56 ` Phil.Edworthy at renesas.com
2014-03-25 21:03 ` Simon Horman
2014-03-26 8:54 ` Phil.Edworthy at renesas.com
2014-03-25 16:56 ` [PATCH v5 7/9] ARM: shmobile: Add PCIe device tree nodes for R8A7791 Koelsch board Phil Edworthy
2014-03-25 21:00 ` Simon Horman
2014-03-25 16:56 ` [PATCH v5 8/9] ARM: koelsch: Add PCIe to defconfig Phil Edworthy
2014-03-25 20:57 ` Simon Horman
2014-03-25 16:56 ` [PATCH v5 9/9] ARM: koelsch: Add HAVE_ARM_ARCH_TIMER " Phil Edworthy
2014-03-25 21:02 ` Simon Horman
2014-03-26 5:39 ` Magnus Damm
2014-03-26 8:50 ` Phil.Edworthy at renesas.com
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=14997425.EPjrKhVy10@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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