linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: b32955@freescale.com (Huang Shijie)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dma: add new DMA control commands
Date: Thu, 18 Oct 2012 14:45:41 +0800	[thread overview]
Message-ID: <507FA595.4020507@freescale.com> (raw)
In-Reply-To: <1350541111.5263.3.camel@vkoul-udesk3>

? 2012?10?18? 14:18, Vinod Koul ??:
> Why cant you do start (prepare clock etc) when you submit the descriptor
> to dmaengine. Can be done in tx_submit callback.
> Similarly remove the clock when dma transaction gets completed.
I ever thought this method too.

But it will become low efficient in the following case:

   Assuming the gpmi-nand driver has to read out 1024 pages in one 
_SINGLE_ read operation.
The gpmi-nand will submit the descriptor to dmaengine per page. So with 
your method,
the system will repeat the enable/disable dma clock 1024 time. At every 
enable/disable dma clock,
the system has to enable the clock chain and it's parents ...

But with this patch, we only need to enable/disable dma clock one time, 
just at we select the nand chip.

thanks
Huang Shijie

  reply	other threads:[~2012-10-18  6:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-18  5:32 [PATCH] dma: add new DMA control commands Huang Shijie
2012-10-18  6:18 ` Vinod Koul
2012-10-18  6:45   ` Huang Shijie [this message]
2012-10-18  7:14     ` Marek Vasut
2012-10-18  7:49       ` Huang Shijie
2012-10-18  8:16         ` Marek Vasut
2012-10-18  8:29           ` Huang Shijie
2012-11-09 15:29             ` Artem Bityutskiy
2012-10-18  8:49           ` Huang Shijie
2012-10-18  8:49             ` Marek Vasut
2012-10-18  9:13               ` Huang Shijie
2012-10-18 10:51                 ` Marek Vasut
2012-10-18 15:11                   ` Huang Shijie
2012-10-18  8:52     ` Russell King - ARM Linux
2012-10-18  9:10       ` Huang Shijie
2012-10-18  9:29     ` Jassi Brar
2012-10-18 15:18       ` Huang Shijie
2012-10-18 15:25         ` Jassi Brar

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=507FA595.4020507@freescale.com \
    --to=b32955@freescale.com \
    --cc=linux-arm-kernel@lists.infradead.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).