From: Kazuhiro Kasai <kasai.kazuhiro@socionext.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: robh+dt@kernel.org, mark.rutland@arm.com,
dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
orito.takao@socionext.com, sugaya.taichi@socionext.com,
kanematsu.shinji@socionext.com, jaswinder.singh@linaro.org,
masami.hiramatsu@linaro.org, linux-kernel@vger.kernel.org,
kasai.kazuhiro@socionext.com
Subject: Re: [PATCH 2/2] dmaengine: milbeaut: Add Milbeaut AXI DMA controller
Date: Tue, 7 May 2019 14:39:24 +0900 [thread overview]
Message-ID: <20190507053924.GA3359@ubuntu> (raw)
In-Reply-To: <20190426114629.GU28103@vkoul-mobl>
Thank you very much for reviewing my patch.
Sorry for my late reply. Japan was in Spring Vacation.
On Fri, Apr 26, 2019 at 17:16 +0530, Vinod Koul wrote:
> On 25-03-19, 13:15, Kazuhiro Kasai wrote:
> > Add Milbeaut AXI DMA controller. This DMA controller has
> > only capable of memory to memory transfer.
>
> Have you tested this with dmatest?
Yes, I have tested this with dmatest.
I use dmatest with the following parameter.
>echo 10 > iterations
>echo "" > channel
>echo 1 > run
And I got the below report from dmatest.
[11675.231268] dmatest: dma0chan0-copy0: summary 10 tests, 0 failures 6910.84 iops 67035 KB/s (0)
[ 5646.689234] dmatest: dma0chan1-copy0: summary 10 tests, 0 failures 7949.12 iops 59618 KB/s (0)
[12487.712996] dmatest: dma0chan2-copy0: summary 10 tests, 0 failures 1493.87 iops 15088 KB/s (0)
[12487.733932] dmatest: dma1chan0-copy0: summary 10 tests, 0 failures 490.98 iops 3142 KB/s (0)
[11675.282428] dmatest: dma1chan2-copy0: summary 10 tests, 0 failures 7112.37 iops 56187 KB/s (0)
[ 5646.754230] dmatest: dma1chan3-copy0: summary 10 tests, 0 failures 6609.38 iops 61467 KB/s (0)
[ 5043.009255] dmatest: dma0chan3-copy0: summary 10 tests, 0 failures 498.08 iops 4183 KB/s (0)
[ 5043.018385] dmatest: dma1chan1-copy0: summary 10 tests, 0 failures 350.62 iops 3155 KB/s (0)
>
> > +struct m10v_dma_chan {
> > + struct dma_chan chan;
> > + struct m10v_dma_device *mdmac;
> > + void __iomem *regs;
> > + int irq;
> > + struct m10v_dma_desc mdesc;
>
> So there is a *single* descriptor? Not a list??
Yes, single descriptor.
>
> > +static void m10v_xdmac_disable_dma(struct m10v_dma_device *mdmac)
> > +{
> > + unsigned int val;
> > +
> > + val = readl(mdmac->regs + M10V_XDACS);
> > + val &= ~M10V_XDACS_XE;
> > + val |= FIELD_PREP(M10V_XDACS_XE, 0);
> > + writel(val, mdmac->regs + M10V_XDACS);
>
> Why not create a modifyl() macro and use it here
Thank you for advise, I will creat modifyl() macro and use it in next version.
>
> > +static void m10v_xdmac_issue_pending(struct dma_chan *chan)
> > +{
> > + struct m10v_dma_chan *mchan = to_m10v_dma_chan(chan);
> > +
> > + m10v_xdmac_config_chan(mchan);
> > +
> > + m10v_xdmac_enable_chan(mchan);
>
> You dont check if anything is already running or not?
Yes, I think I don't need check if dma is running or not.
Because there's a single descriptor.
>
> > +static dma_cookie_t m10v_xdmac_tx_submit(struct dma_async_tx_descriptor *txd)
> > +{
> > + struct m10v_dma_chan *mchan = to_m10v_dma_chan(txd->chan);
> > + dma_cookie_t cookie;
> > + unsigned long flags;
> > +
> > + spin_lock_irqsave(&mchan->lock, flags);
> > + cookie = dma_cookie_assign(txd);
> > + spin_unlock_irqrestore(&mchan->lock, flags);
> > +
> > + return cookie;
>
> sounds like vchan_tx_submit() i think you can use virt-dma layer and then
> get rid of artificial limit in driver and be able to queue up the txn on
> dmaengine.
OK, I will try to use virt-dma layer in next version.
>
> > +static struct dma_async_tx_descriptor *
> > +m10v_xdmac_prep_dma_memcpy(struct dma_chan *chan, dma_addr_t dst,
> > + dma_addr_t src, size_t len, unsigned long flags)
> > +{
> > + struct m10v_dma_chan *mchan = to_m10v_dma_chan(chan);
> > +
> > + dma_async_tx_descriptor_init(&mchan->mdesc.txd, chan);
> > + mchan->mdesc.txd.tx_submit = m10v_xdmac_tx_submit;
> > + mchan->mdesc.txd.callback = NULL;
> > + mchan->mdesc.txd.flags = flags;
> > + mchan->mdesc.txd.cookie = -EBUSY;
> > +
> > + mchan->mdesc.len = len;
> > + mchan->mdesc.src = src;
> > + mchan->mdesc.dst = dst;
> > +
> > + return &mchan->mdesc.txd;
>
> So you support single descriptor and dont check if this has been already
> configured. So I guess this has been tested by doing txn one at a time
> and not submitted bunch of txn and wait for them to complete. Please fix
> that to really enable dmaengine capabilities.
Thank you for advice. I want to fix it and I have 2 questions.
1. Does virt-dma layer help to fix this?
2. Can dmatest test that dmaengine capabilities?
>
> > +static int m10v_xdmac_remove(struct platform_device *pdev)
> > +{
> > + struct m10v_dma_chan *mchan;
> > + struct m10v_dma_device *mdmac = platform_get_drvdata(pdev);
> > + int i;
> > +
> > + m10v_xdmac_disable_dma(mdmac);
> > +
> > + for (i = 0; i < mdmac->channels; i++) {
> > + mchan = &mdmac->mchan[i];
> > + devm_free_irq(&pdev->dev, mchan->irq, mchan);
> > + }
>
> No call to dma_async_device_unregister()?
Thank you, I will call dma_async_device_unregister in next version.
Thanks,
Kasai
next prev parent reply other threads:[~2019-05-07 5:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1553487314-9185-1-git-send-email-kasai.kazuhiro@socionext.com>
2019-03-25 4:15 ` [2/2] dmaengine: milbeaut: Add Milbeaut AXI DMA controller Kazuhiro Kasai
2019-04-16 2:06 ` Kazuhiro Kasai
2019-04-16 2:06 ` [PATCH 2/2] " Kazuhiro Kasai
2019-04-26 11:46 ` [2/2] " Vinod Koul
2019-04-26 11:46 ` [PATCH 2/2] " Vinod Koul
2019-05-07 5:39 ` Kazuhiro Kasai [this message]
2019-05-07 17:10 ` Vinod Koul
2019-05-07 23:37 ` Kazuhiro Kasai
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=20190507053924.GA3359@ubuntu \
--to=kasai.kazuhiro@socionext.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=jaswinder.singh@linaro.org \
--cc=kanematsu.shinji@socionext.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=masami.hiramatsu@linaro.org \
--cc=orito.takao@socionext.com \
--cc=robh+dt@kernel.org \
--cc=sugaya.taichi@socionext.com \
--cc=vkoul@kernel.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).