public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shengjiu Wang <shengjiu.wang@freescale.com>
To: Vinod Koul <vinod.koul@intel.com>
Cc: <dan.j.williams@intel.com>, <dmaengine@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dmaengine: imx-sdma: Add device to device support
Date: Fri, 10 Jul 2015 13:44:35 +0800	[thread overview]
Message-ID: <20150710054433.GA14762@shlinux2> (raw)
In-Reply-To: <20150710062205.GA836@localhost>

On Fri, Jul 10, 2015 at 11:52:05AM +0530, Vinod Koul wrote:
> On Tue, Jul 07, 2015 at 01:24:22PM +0800, Shengjiu Wang wrote:
> > > why not use set_bit(), you are modifying driver memory
> > Original driver all use the __set_bit. do you think we need to change
> > all the __set_bit to set_bit? And from the header file "arch/arm/include/asm
> > /bitops.h", the set_bit is same as __set_bit.
> New changes should be rightly done. __xxx denotes typically internal API to
> a subsystem, so if they are same I would suggest to use set_bit()
Ok, I agree with you.
> 
> > > > +	/*
> > > > +	 * If LWML(src_maxburst) > HWML(dst_maxburst), we need
> > > > +	 * swap LWML and HWML of INFO(A.3.2.5.1), also need swap
> > > > +	 * r0(event_mask[1]) and r1(event_mask[0]).
> > > > +	 */
> > > > +	if (lwml > hwml) {
> > > > +		sdmac->watermark_level &= ~0xff00ff;
> > > Magic number?
> ??
I have add a description on V2 patch for the watermark_level definition.
> 
> > > Okay the direction is depreciated, so can you store both source and
> > > destination and use them based on direction in prepare()
> > > 
> > > Also I see driver is not doing this, so while at it, can you fix this is
> > > current code as well
> > > 
> > which prepare() do you mean? sdma_prep_dma_cyclic, sdma_prep_slave_sg?
> both have direction as an argument. So you need to use that
I have removed the direction checking. So I think don't need to change the
sdma_prep_dma_cyclic, sdma_prep_slave_sg.

Anyway please review the V2 patch for this, I have sent it out. In V2, I still
use the __set_bit. After you review the V2 patch, I will change them together.

Thanks.
wang shengjiu
> 
> -- 
> ~Vinod
> 

      reply	other threads:[~2015-07-10  6:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-23  8:42 [PATCH] dmaengine: imx-sdma: Add device to device support Shengjiu Wang
2015-07-07  4:20 ` Vinod Koul
2015-07-07  5:24   ` Shengjiu Wang
2015-07-07  8:12     ` Shengjiu Wang
2015-07-10  6:22     ` Vinod Koul
2015-07-10  5:44       ` Shengjiu Wang [this message]

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=20150710054433.GA14762@shlinux2 \
    --to=shengjiu.wang@freescale.com \
    --cc=dan.j.williams@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vinod.koul@intel.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