From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/5] ARM: highbank: enable DMA zone for LPAE
Date: Tue, 6 Aug 2013 01:11:27 +0100 [thread overview]
Message-ID: <20130806001127.GA23006@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1375743009-28972-3-git-send-email-robherring2@gmail.com>
On Mon, Aug 05, 2013 at 05:50:07PM -0500, Rob Herring wrote:
> From: Rob Herring <rob.herring@calxeda.com>
>
> Some devices are restricted to 32-bit DMA. Thus the platform dma_zone_size
> needs to be set. Otherwise dma-mapping code is complaining, e.g.
>
> calxedaxgmac fff50000.ethernet: coherent DMA mask 0xffffffff is smaller
> than system GFP_DMA mask 0xffffffffffffffff
Note that the patches I posted last week will fix that in a much nicer
way, as we will only error if we actually have sufficient memory that
the condition becomes problematical.
The other problem here is that we need to get better separation between
what's a bus address and what's a physical address.
next prev parent reply other threads:[~2013-08-06 0:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 22:50 [PATCH 1/5] ARM: use phys_addr_t for DMA zone sizes Rob Herring
2013-08-05 22:50 ` [PATCH 2/5] ARM: make dma_addr_t 64-bit on LPAE Rob Herring
2013-08-06 0:15 ` Russell King - ARM Linux
2013-08-06 1:59 ` Rob Herring
2013-08-14 13:03 ` Russell King - ARM Linux
2013-08-05 22:50 ` [PATCH 3/5] ARM: highbank: enable DMA zone for LPAE Rob Herring
2013-08-06 0:11 ` Russell King - ARM Linux [this message]
2013-08-06 3:29 ` Rob Herring
2013-08-05 22:50 ` [PATCH 4/5] ARM: highbank: select ARCH_HAS_HOLES_MEMORYMODEL Rob Herring
2013-08-05 22:50 ` [PATCH 5/5] ARM: highbank: select required errata work-arounds Rob Herring
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=20130806001127.GA23006@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).