From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH RFC 0/2] ARM: shmobile: lager: Enable DMA bounce for PCI
Date: Wed, 29 Jan 2014 06:45:21 +0000 [thread overview]
Message-ID: <20140129064521.GI23833@verge.net.au> (raw)
In-Reply-To: <1390935213-12896-1-git-send-email-valentine.barshak@cogentembedded.com>
On Tue, Jan 28, 2014 at 10:53:31PM +0400, Valentine Barshak wrote:
> This enables DMA bounce for PCI since the controller does
> not support more than 2G PCI-AHB memory window.
> The problems with DMA transfers can be observed when
> setting 2G/2G user/kernel memory split model
> (CONFIG_VMSPLIT_2G=y)
> These patches help to avoid it.
Are these patches compatible with other user/kernel splits?
>
> The patches should be applied on top of the
> "[PATCH V3 0/3] ARM: shmobile: lager: Add USB support" series at
> http://marc.info/?l=linux-sh&m\x139060253506760&w=2
>
> Valentine Barshak (2):
> ARM: shmobile: lager: Use DMA bounce for PCI devices
> ARM: shmobile: lager: Increase the size of ARM corehent DMA pool
>
> arch/arm/boot/dts/r8a7790-lager.dts | 2 +-
> arch/arm/mach-shmobile/Kconfig | 2 ++
> arch/arm/mach-shmobile/board-lager.c | 38 ++++++++++++++++++++++++++++++++++++
> 3 files changed, 41 insertions(+), 1 deletion(-)
>
> --
> 1.8.3.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sh" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2014-01-29 6:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 18:53 [PATCH RFC 0/2] ARM: shmobile: lager: Enable DMA bounce for PCI Valentine Barshak
2014-01-29 6:45 ` Simon Horman [this message]
2014-01-29 8:03 ` Ben Dooks
2014-01-29 9:38 ` Valentine
2014-01-29 11:15 ` Valentine
2014-01-29 12:45 ` Ben Dooks
2014-01-29 12:47 ` Valentine
2014-01-29 16:03 ` Ben Dooks
2014-01-29 16:37 ` Valentine
2014-01-29 16:57 ` Ben Dooks
2014-01-29 17:05 ` Valentine
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=20140129064521.GI23833@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-sh@vger.kernel.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).