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 0/2] ARM: shmobile: lager: Enable DMA bounce for PCI
Date: Wed, 29 Jan 2014 11:15:23 +0000	[thread overview]
Message-ID: <52E8E2CB.6070405@cogentembedded.com> (raw)
In-Reply-To: <1390935213-12896-1-git-send-email-valentine.barshak@cogentembedded.com>

On 01/29/2014 12:03 PM, Ben Dooks wrote:
> On 29/01/14 06:45, Simon Horman wrote:
>> 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?
>
> PS, the bridge is only actually capable of seeing 1GiB of
> RAM due to alignment issues in the window. You can have either
> 0x4..0x8 or 0x8..0xc but not /both/. If you open the window to
> 2GiB then you can see either 0x0..0x8 or 0x8..0xF range.
>

I don't think this is relater to the user/kernel space memory split.

Currently the R-Car Gen2 PCI driver uses 0x40000000 - 0x7fffffff
PCI-AHB region. We can set it to 0x00000000 - 0x7fffffff,
but there's no RAM below 0x40000000 so no DMA access to that area is
actually legal from the PCI USB host driver.
So the change wouldn't give us much.

The 31-bit DMA mask takes care of forbidding any DMA transfers
to the area above 0x7fffffff.

Thanks,
Val.




  parent reply	other threads:[~2014-01-29 11:15 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
2014-01-29  8:03 ` Ben Dooks
2014-01-29  9:38 ` Valentine
2014-01-29 11:15 ` Valentine [this message]
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=52E8E2CB.6070405@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).