linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] dmaengine: Add hisilicon k3 DMA engine driver
Date: Sun, 25 Aug 2013 14:44:35 +0530	[thread overview]
Message-ID: <20130825091435.GI8091@intel.com> (raw)
In-Reply-To: <CAMj5BkhKwG3PuaCS=m7No9V8w2tMbeYnmJr+B_fUQJnSZW6QPw@mail.gmail.com>

On Wed, Aug 21, 2013 at 04:02:03PM +0800, zhangfei gao wrote:
> Excuse me for my bad English.
> I am really lost and don't know what to do now.
> Are you concern:
> 1. Why need else in case DMA_PAUSE, no need?
> 2. device_tx_status is not called in audio and directly
> dmaengine_pause -> dmaengine_resume?
> 3. ?
> 
> Besides, where I should take example of amba-pl08x.c, pl08x_control,
> case DMA_PAUSE & DMA_RESUME or pl08x_dma_tx_status?
> 
> Some difference I see is k3dma.c only has one tasklet for all channels,
> The tasklet will check pending channel and alloc physical channel.
> While the issue_pending does not really alloc physical channel to
> support more request then physical channel.
> So when suspend we have to consider remove the channel from chan_pending.
> 
> When trying use virt-dma, have study drivers/dma/sa11x0-dma.c as good reference.
> 
> Sorry for my bad understanding.
No issues...

I think i am okay with else part looking at the driver again.

Can you resend by rebasing on my next and fxing any other issues

~Vinod
-- 

  reply	other threads:[~2013-08-25  9:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-28 12:39 [PATCH v2 0/2] dmaengine: add k3dma Zhangfei Gao
2013-06-28 12:39 ` [PATCH v2 1/2] dmaengine: add interface of dma_get_slave_channel Zhangfei Gao
2013-06-28 14:32   ` Arnd Bergmann
2013-08-13 11:04   ` Vinod Koul
2013-06-28 12:39 ` [PATCH v2 2/2] dmaengine: Add hisilicon k3 DMA engine driver Zhangfei Gao
2013-08-13 11:20   ` Vinod Koul
2013-08-15  5:54     ` zhangfei gao
2013-08-19  5:35       ` Vinod Koul
2013-08-20  7:55         ` zhangfei gao
2013-08-20  8:27           ` Vinod Koul
2013-08-20  9:23             ` zhangfei
2013-08-20  8:50               ` Vinod Koul
2013-08-20 13:36                 ` zhangfei gao
2013-08-21  4:58                   ` Vinod Koul
2013-08-21  8:02                     ` zhangfei gao
2013-08-25  9:14                       ` Vinod Koul [this message]
2013-08-22  1:39                     ` zhangfei gao

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=20130825091435.GI8091@intel.com \
    --to=vinod.koul@intel.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).