mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pierre Ossman <pierre@ossman.eu>
To: "Ramesh.R" <ramesh.kvp@gmail.com>
Cc: linux-kernel@vger.kernel.org, srini@arasan.com, ramesh@arasan.com
Subject: Re: 64 bit Descriptors in ADMA of Linux SDHost controller driver.
Date: Fri, 2 Apr 2010 19:16:00 +0200	[thread overview]
Message-ID: <20100402191600.19af3ffc@mjolnir.ossman.eu> (raw)
In-Reply-To: <p2r1e3142441004011446r707284b7p2cd5e3046719c2ed@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1811 bytes --]

On Thu, 1 Apr 2010 14:46:14 -0700
"Ramesh.R" <ramesh.kvp@gmail.com> wrote:

> Hi Pierre Ossman,
> 
> When we go though the Linux Standard SD Host controller driver(Using the
> Kernel 2.6.33), we saw only the 32 bit Descriptors implemented in it.
> 
> We confirmed this status for 32 bit and 64 bit processors.
> 
> Are these observations correct. Please clarify us.
> 

Quite. The hardware I had at my disposal only supported 32-bit
descriptors and I didn't want to write code that I had no way of
testing.

> Also how the 64 bit machines will process the data, if the Descriptors are
> implemented with 32 bit. If they are using the 32 bit and don't care about
> the MSB 32 bits, then there is no major difference in performance wise,
> whether it is 32 or 64 bit processors. Please correct me if my understanding
> is wrong.

The only performance impact that might occur is if you try to transfer
to/from an address above 4 GiB, at which point you need a bounce buffer
and an extra memory copy.

(I believe the kernel does this by default if the driver doesn't
explicitly say that it is 64-bit compatible)

> 
> Also please point us, if we need to use 64 bit addressing for DMA
> descriptors is there any way with the current SD host controller or not.
> 

It's been quite some time since I looked at the driver, but I seem to
recall that adding 64-bit support is not a particularly difficult task.
As long as you have hardware for testing then it is something that you
should be able to sort out with less than a week of work.

Rgds
-- 
     -- Pierre Ossman

  WARNING: This correspondence is being monitored by FRA, a
  Swedish intelligence agency. Make sure your server uses
  encryption for SMTP traffic and consider using PGP for
  end-to-end encryption.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

           reply	other threads:[~2010-04-02 17:21 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <p2r1e3142441004011446r707284b7p2cd5e3046719c2ed@mail.gmail.com>]

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=20100402191600.19af3ffc@mjolnir.ossman.eu \
    --to=pierre@ossman.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ramesh.kvp@gmail.com \
    --cc=ramesh@arasan.com \
    --cc=srini@arasan.com \
    /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

all inboxes | Powered by JetHome®