All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Christopher Freeman <cfreeman@nvidia.com>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
	Laxman Dewangan <ldewangan@nvidia.com>,
	Stephen Warren <swarren@nvidia.com>,
	"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
	"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 1/3] dma: tegra: finer granularity residual for tx_status
Date: Wed, 21 May 2014 11:30:12 +0530	[thread overview]
Message-ID: <20140521060012.GL21128@intel.com> (raw)
In-Reply-To: <20140507223745.GB20137@nvidia.com>

On Wed, May 07, 2014 at 03:37:45PM -0700, Christopher Freeman wrote:
> On Wed, May 07, 2014 at 09:37:25AM -0700, Stephen Warren wrote:
> > On 05/06/2014 03:22 PM, Christopher Freeman wrote:
> > > Get word-level granularity from hardware for calculating
> > > the transfer count remaining.
> > 
> > > diff --git a/drivers/dma/tegra20-apb-dma.c b/drivers/dma/tegra20-apb-dma.c
> > 
> > > +static int tegra_dma_wcount_in_bytes(struct dma_chan *dc)
> > 
> > A lot of the code in this function is identical to the code in
> > tegra_dma_terminate_all() which does the same thing. Can this be pulled
> > out into a shared utility function?
> > 
> I'll look at making utility functions for ISR handling and the calculations for the byte counts.
> 
> > > +	tegra_dma_pause(tdc, true);
> > 
> > Is this continual pausing/resuming of the DMA operation going to
> > negatively affect performance?
> > 
> I tried testing the performance impact and each call took about 20 uS.  And of
> course, the client would have to be calling this constantly.
But why do we need to pause, cant we read the status form HW and report..?

-- 
~Vinod

  parent reply	other threads:[~2014-05-21  6:00 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-06 21:22 [PATCH v1 0/3] Tegra DMA residue improvements Christopher Freeman
2014-05-06 21:22 ` Christopher Freeman
2014-05-06 21:22 ` [PATCH v1 1/3] dma: tegra: finer granularity residual for tx_status Christopher Freeman
2014-05-06 21:22   ` Christopher Freeman
2014-05-07 16:37   ` Stephen Warren
     [not found]     ` <536A6145.2080106-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-05-07 22:37       ` Christopher Freeman
2014-05-07 22:37         ` Christopher Freeman
     [not found]         ` <20140507223745.GB20137-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2014-05-12 17:27           ` Stephen Warren
2014-05-12 17:27             ` Stephen Warren
2014-05-21  6:00         ` Vinod Koul [this message]
2014-05-06 21:22 ` [PATCH v1 2/3] dma: tegra: change interrupt-related log levels Christopher Freeman
2014-05-06 21:22   ` Christopher Freeman
     [not found] ` <1399411343-12222-1-git-send-email-cfreeman-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2014-05-06 21:22   ` [PATCH v1 3/3] dma: tegra: avoid int overflow for transferred count Christopher Freeman
2014-05-06 21:22     ` Christopher Freeman
2014-05-07 16:38     ` Stephen Warren
     [not found]       ` <536A61A3.3050601-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-05-07 19:15         ` Lars-Peter Clausen
2014-05-07 19:15           ` Lars-Peter Clausen
2014-05-07 22:50           ` Christopher Freeman
2014-05-07  6:38 ` [PATCH v1 0/3] Tegra DMA residue improvements Lars-Peter Clausen
     [not found]   ` <5369D4FF.1070004-Qo5EllUWu/uELgA04lAiVw@public.gmane.org>
2014-05-07 21:27     ` Christopher Freeman
2014-05-07 21:27       ` Christopher Freeman
2014-05-21  5:52 ` Vinod Koul
     [not found]   ` <20140521055213.GK21128-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-05-21  6:58     ` Lars-Peter Clausen
2014-05-21  6:58       ` Lars-Peter Clausen
2014-05-21 11:06       ` Vinod Koul
2014-05-21 16:21         ` Stephen Warren

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=20140521060012.GL21128@intel.com \
    --to=vinod.koul@intel.com \
    --cc=cfreeman@nvidia.com \
    --cc=dan.j.williams@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=ldewangan@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=swarren@nvidia.com \
    --cc=swarren@wwwdotorg.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 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.