From: Vinod Koul <vkoul@kernel.org>
To: Robin Gong <yibin.gong@nxp.com>
Cc: "dan.j.williams@intel.com" <dan.j.williams@intel.com>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
dl-linux-imx <linux-imx@nxp.com>
Subject: [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)
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
next reply other threads:[~2018-07-11 7:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 7:12 Vinod Koul [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-07-11 7:08 [v1,1/4] dmaengine: imx-sdma: add memcpy interface Sascha Hauer
2018-07-11 7:05 Robin Gong
2018-07-11 7:01 Sascha Hauer
2018-07-11 6:56 Robin Gong
2018-07-11 6:24 Sascha Hauer
2018-07-11 5:34 Robin Gong
2018-07-10 16:23 Robin Gong
2018-07-10 15:29 Vinod Koul
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=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=yibin.gong@nxp.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