public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Alexandre Courbot <acourbot@nvidia.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
	Thierry Reding <thierry.reding@gmail.com>,
	linux-mmc@vger.kernel.org, linux-tegra@vger.kernel.org,
	linux-kernel@vger.kernel.org, gnurou@gmail.com
Subject: Re: [PATCH] mmc: sdhci-tegra: Set DMA mask
Date: Wed, 24 Feb 2016 10:08:54 -0700	[thread overview]
Message-ID: <56CDE3A6.9080903@wwwdotorg.org> (raw)
In-Reply-To: <1456305079-27779-1-git-send-email-acourbot@nvidia.com>

On 02/24/2016 02:11 AM, Alexandre Courbot wrote:
> On T210, the sdhci controller can address more than 32 bits of address
> space. Failing to express this fact results in the use of bounce
> buffers and affects performance.
>
> Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>
> ---
> I am pretty sure this one is wrong in some way, but just to get the ball
> rolling as the use of bounce buffers is currently quite heavy on Jetson TX1.
>
> Thierry, Stephen, could you confirm that I got the DMA masks correctly? I
> am not sure about the actual addressable size on TX1, and also suspect TK1 can
> also address more than 32 bits.

I don't actually know what the HW capabilities are. You had best track 
down one of NVIDIA's HW designers/integrators; hopefully the can provide 
all kinds of gory details.

One thing I will say: in U-Boot, we deliberately clip usable RAM size to 
2GiB so that the PA of all RAM fits into 32 bits, specifically because 
of IO controllers that can only address 32 bits. It is possible this was 
only required on earlier chips and T210 fixed it though; I don't know. 
Equally, I suppose the restriction might only apply to a subset of IO 
controllers (USB would be another one relevant to U-Boot).

      parent reply	other threads:[~2016-02-24 17:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24  9:11 [PATCH] mmc: sdhci-tegra: Set DMA mask Alexandre Courbot
2016-02-24 12:37 ` Arnd Bergmann
2016-02-25  9:49   ` Alexandre Courbot
2016-02-25 14:52     ` Arnd Bergmann
2016-02-26  7:24       ` Alexandre Courbot
2016-02-26 11:31         ` Arnd Bergmann
2016-03-01  4:21           ` Alexandre Courbot
2016-02-24 17:08 ` Stephen Warren [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=56CDE3A6.9080903@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=acourbot@nvidia.com \
    --cc=gnurou@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=thierry.reding@gmail.com \
    --cc=ulf.hansson@linaro.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