All of lore.kernel.org
 help / color / mirror / Atom feed
From: geomatsi <geomatsi@gmail.com>
To: Matej Kupljen <matej.kupljen@norik.com>
Cc: Jeff Garzik <jgarzik@redhat.com>,
	nicolas.ferre@atmel.com, linux-ide@vger.kernel.org
Subject: Re: DMA support for CF
Date: Tue, 18 Dec 2012 21:59:44 +0000	[thread overview]
Message-ID: <50D0E750.6070406@gmail.com> (raw)
In-Reply-To: <50D0264C.1010907@norik.com>

On 12/18/2012 08:16 AM, Matej Kupljen wrote:
> Dear Sergey and Jeff,

> I have a board based on AT91SAM9263, with the CF connected to
> the EBI0 and I am using the pata-at91.c driver.
>
> My question is, can I use DMA (MWDMA and/or UDMA) for the CF card,
> of course, if I add support to the driver?
> Basically, the question is, can we use the HDMAC (DMA controller)
> to support the DMA transfers?
> Please note that the DMARQ and DMACK are connected from CF to SoC.
>
>
> I've been looking for this in the documentation, and I cannot find the
> answer. Considering that the SAM9263 is considered legacy, I have
> checked the documentation for AT91SAM9R/RL and AT91SAM9G and I couldn't
> find the answer there either.
>
> Can you answer this question, please?
> If not, to whom I should send it?
>
> Thank you and Best Regards,
> Matej Kupljen

Hi,

In the future could you please consider sending your questions to a 
proper kernel mail list cc-ing authors/maintainers if necessary.


As you noted, driver pata-at91 does not have dma support. This is 
because originally it has been developed for a board based on 
at91sam9260 chip which has no dma engine. More recent at91 chips 
(including at91sam9263) do have dma engines. It should be possible to 
add dma support to pata-at91 driver and use dma transfers for CF.

A couple of notes regarding at91sam9263:

1. DMA driver
IIRC at91sam9263 chip has a different dma engine than all the other 
chips of at91 family. More recent chips have HDMAC: 
drivers/dma/at_hdmac.c while at91sam9263 has DWDMA: drivers/dma/dw_dmac.c

2. Size of dma transfers
IIRC there is a problem with dma engine on at91sam9263 chip: it has 
significantly reduced block size for transfers. This leads into a fairly 
small max transfer size in a single block transfer. As a result, it 
might not be practical to use this particular dma engine for CF.

Thanks,
Sergey

       reply	other threads:[~2012-12-18 18:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <50D0264C.1010907@norik.com>
2012-12-18 21:59 ` geomatsi [this message]
2012-12-19  8:32   ` DMA support for CF Matej Kupljen

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=50D0E750.6070406@gmail.com \
    --to=geomatsi@gmail.com \
    --cc=jgarzik@redhat.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=matej.kupljen@norik.com \
    --cc=nicolas.ferre@atmel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.