public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: vkoul@kernel.org (Vinod)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 1/4] dmaengine: imx-sdma: add memcpy interface
Date: Wed, 11 Jul 2018 12:42:06 +0530	[thread overview]
Message-ID: <20180711071206.GM3219@vkoul-mobl> (raw)
In-Reply-To: <DB6PR04MB32234F1EE6F457E0D8D12385895A0@DB6PR04MB3223.eurprd04.prod.outlook.com>

On 11-07-18, 05:34, Robin Gong wrote:
> > On 11-07-18, 00:23, Robin Gong wrote:
> > > Add MEMCPY support, meanwhile, add SDMA_BD_MAX_CNT instead of
> > > '0xffff'.
> > 
> > latter part should be its own patch. Never mix things
> Okay, I will split it even for this minor change.

Yes, a patch should represent _one_ thing, describe that one thing and
do that one thing.

Anything else, doesn't matter how simple or complex should be an
individual patch

> > > +	if (!desc)
> > > +		goto err_out;
> > > +
> > > +	do {
> > > +		count = min_t(size_t, len, SDMA_BD_MAX_CNT);
> > > +		bd = &desc->bd[i];
> > > +		bd->buffer_addr = dma_src;
> > > +		bd->ext_buffer_addr = dma_dst;
> > > +		bd->mode.count = count;
> > > +		desc->chn_count += count;
> > > +
> > > +		switch (sdmac->word_size) {
> > > +		case DMA_SLAVE_BUSWIDTH_4_BYTES:
> > 
> > This looks wrong, we are in memcpy, there is no SLAVE so no SLAVE widths..
> > 
> Okay, will remove check bus width.

it is not about bus_width but the fact that you are using slave
concepts. In memcpy we have _no_ slave, hence do not use anything
related to slave including dma_slave_config

-- 
~Vinod

  reply	other threads:[~2018-07-11  7:12 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-10 16:23 [PATCH v1 0/4] add memcpy support for sdma Robin Gong
2018-07-10 16:23 ` [PATCH v1 1/4] dmaengine: imx-sdma: add memcpy interface Robin Gong
2018-07-10 15:29   ` Vinod
2018-07-11  5:34     ` Robin Gong
2018-07-11  7:12       ` Vinod [this message]
2018-07-11  6:24   ` Sascha Hauer
2018-07-11  6:56     ` Robin Gong
2018-07-11  7:01       ` Sascha Hauer
2018-07-11  7:05         ` Robin Gong
2018-07-11  7:08           ` Sascha Hauer
2018-07-10 16:23 ` [PATCH v1 2/4] dmaengine: imx-sdma: add check_bd_buswidth() to kill the dulicated code Robin Gong
2018-07-10 15:31   ` Vinod
2018-07-11  5:36     ` Robin Gong
2018-07-11  6:32   ` Sascha Hauer
2018-07-10 16:23 ` [PATCH v1 3/4] dmaengine: imx-sdma: support dmatest Robin Gong
2018-07-10 15:33   ` Vinod
2018-07-11  6:37     ` Robin Gong
2018-07-11  6:53       ` s.hauer at pengutronix.de
2018-07-11  7:14         ` Robin Gong
2018-07-11  7:19         ` Vinod
2018-07-11  8:16           ` Robin Gong
2018-07-11  8:58             ` Vinod
2018-07-10 16:23 ` [PATCH v1 4/4] ARM: configs: imx_v6_v7_defconfig: add DMATEST support Robin Gong

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=20180711071206.GM3219@vkoul-mobl \
    --to=vkoul@kernel.org \
    --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