linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Valentine <valentine.barshak@cogentembedded.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH RFC 2/2] ARM: shmobile: lager: Increase the size of ARM corehent DMA pool
Date: Wed, 29 Jan 2014 09:52:33 +0000	[thread overview]
Message-ID: <52E8CF61.1010907@cogentembedded.com> (raw)
In-Reply-To: <1390935213-12896-3-git-send-email-valentine.barshak@cogentembedded.com>

On 01/29/2014 01:07 PM, Ben Dooks wrote:
> On 28/01/14 18:53, Valentine Barshak wrote:
>> This increases the size of ARM coherent DMA pool to 4MB to
>> avoid issues with DMA bounce for PCI DMA transfers.
>
> Would it be easier to enable CMA support given that the DU
> driver really needs it.
>

It doesn't help since dmabounce driver does not allocate bounce buffers from CMA.

Thanks,
Val.

      parent reply	other threads:[~2014-01-29  9:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-28 18:53 [PATCH RFC 2/2] ARM: shmobile: lager: Increase the size of ARM corehent DMA pool Valentine Barshak
2014-01-29  9:07 ` Ben Dooks
2014-01-29  9:52 ` Valentine [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=52E8CF61.1010907@cogentembedded.com \
    --to=valentine.barshak@cogentembedded.com \
    --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).