From: Vinod Koul <vkoul@kernel.org>
To: Green Wan <green.wan@sifive.com>
Cc: kbuild test robot <lkp@intel.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Palmer Dabbelt <palmer@sifive.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Dan Williams <dan.j.williams@intel.com>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
"Paul E. McKenney" <paulmck@linux.ibm.com>,
Yash Shah <yash.shah@sifive.com>, Bin Meng <bmeng.cn@gmail.com>,
Sagar Kadam <sagar.kadam@sifive.com>,
dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 3/4] dmaengine: sf-pdma: add platform DMA support for HiFive Unleashed A00
Date: Tue, 5 Nov 2019 23:18:23 +0530 [thread overview]
Message-ID: <20191105174823.GF952516@vkoul-mobl> (raw)
In-Reply-To: <20191028075658.12143-4-green.wan@sifive.com>
On 28-10-19, 15:56, Green Wan wrote:
> Add PDMA driver, sf-pdma, to enable DMA engine on HiFive Unleashed
> Rev A00 board.
>
> - Implement dmaengine APIs, support MEM_TO_MEM async copy.
> - Tested by DMA Test client
> - Supports 4 channels DMA, each channel has 1 done and 1 err
> interrupt connected to platform-level interrupt controller (PLIC).
> - Depends on DMA_ENGINE and DMA_VIRTUAL_CHANNELS
>
> The datasheet is here:
>
> https://static.dev.sifive.com/FU540-C000-v1.0.pdf
>
> Follow the DMAengine controller doc,
> "./Documentation/driver-api/dmaengine/provider.rst" to implement DMA
> engine. And use the dma test client in doc,
> "./Documentation/driver-api/dmaengine/dmatest.rst", to test.
>
> Each DMA channel has separate HW regs and support done and error ISRs.
> 4 channels share 1 done and 1 err ISRs. There's no expander/arbitrator
> in DMA HW.
>
> ------ ------
> | |--< done 23 >--|ch 0|
> | |--< err 24 >--| | (dma0chan0)
> | | ------
> | | ------
> | |--< done 25 >--|ch 1|
> | |--< err 26 >--| | (dma0chan1)
> |PLIC| ------
> | | ------
> | |--< done 27 >--|ch 2|
> | |--< err 28 >--| | (dma0chan2)
> | | ------
> | | ------
> | |--< done 29 >--|ch 3|
> | |--< err 30 >--| | (dma0chan3)
> ------ ------
>
> Reviewed-by: Vinod Koul <vkoul@kernel.org>
when did i provide this?
> Signed-off-by: Green Wan <green.wan@sifive.com>
> Reported-by: kbuild test robot <lkp@intel.com>
> Fixes: 31c3b98b5a01 ("dmaengine: sf-pdma: add platform DMA support for HiFive Unleashed A00")
Fixes what... this is not a upstream commit?
> Signed-off-by: kbuild test robot <lkp@intel.com>
> ---
Please list the changes done from prev version, here or in cover letter
> +static struct sf_pdma_desc *sf_pdma_alloc_desc(struct sf_pdma_chan *chan)
> +{
> + struct sf_pdma_desc *desc;
> + unsigned long flags;
> +
> + spin_lock_irqsave(&chan->lock, flags);
> +
> + if (chan->desc && !chan->desc->in_use) {
> + spin_unlock_irqrestore(&chan->lock, flags);
> + return chan->desc;
> + }
> +
> + spin_unlock_irqrestore(&chan->lock, flags);
> +
> + desc = kzalloc(sizeof(*desc), GFP_NOWAIT);
> +
this empty line in not required
> +static struct dma_async_tx_descriptor *
> + sf_pdma_prep_dma_memcpy(struct dma_chan *dchan,
> + dma_addr_t dest,
please make it left justified
> +static int sf_pdma_slave_config(struct dma_chan *dchan,
> + struct dma_slave_config *cfg)
> +{
> + struct sf_pdma_chan *chan = to_sf_pdma_chan(dchan);
> +
> + memcpy(&chan->cfg, cfg, sizeof(*cfg));
> + chan->dma_dir = DMA_MEM_TO_MEM;
?? looking at changelog we have only memcpy support, so this should not
be here, pls remove this.
> +static enum dma_status
> +sf_pdma_tx_status(struct dma_chan *dchan,
> + dma_cookie_t cookie,
> + struct dma_tx_state *txstate)
> +{
> + struct sf_pdma_chan *chan = to_sf_pdma_chan(dchan);
> + enum dma_status status;
> +
> + status = dma_cookie_status(dchan, cookie, txstate);
> +
> + if (txstate && status != DMA_ERROR)
> + dma_set_residue(txstate, sf_pdma_desc_residue(chan));
which residue? the query can be for a cookie which is still in pending
list! you need to check the cookie and only read register for cookie if
submitted
> +static int sf_pdma_remove(struct platform_device *pdev)
> +{
> + struct sf_pdma *pdma = platform_get_drvdata(pdev);
> + struct sf_pdma_chan *ch;
> + int i;
> +
> + for (i = 0; i < PDMA_NR_CH; i++) {
> + ch = &pdma->chans[i];
> +
> + list_del(&ch->vchan.chan.device_node);
> + tasklet_kill(&ch->vchan.task);
> + tasklet_kill(&ch->done_tasklet);
> + tasklet_kill(&ch->err_tasklet);
you have an isr registered which can fire and schedule tasklets..
--
~Vinod
next prev parent reply other threads:[~2019-11-05 17:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 7:56 [PATCH v5 0/4] dmaengine: sf-pdma: Add platform dma driver Green Wan
2019-10-28 7:56 ` [PATCH v5 1/4] dt-bindings: dmaengine: sf-pdma: add bindins for SiFive PDMA Green Wan
2019-10-28 7:56 ` [PATCH v5 2/4] riscv: dts: add support for PDMA device of HiFive Unleashed Rev A00 Green Wan
2019-10-28 7:56 ` [PATCH v5 3/4] dmaengine: sf-pdma: add platform DMA support for HiFive Unleashed A00 Green Wan
2019-11-05 17:48 ` Vinod Koul [this message]
2019-11-07 2:11 ` Green Wan
2019-10-28 7:56 ` [PATCH v5 4/4] MAINTAINERS: Add Green as SiFive PDMA driver maintainer Green Wan
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=20191105174823.GF952516@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=aou@eecs.berkeley.edu \
--cc=bmeng.cn@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=green.wan@sifive.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lkp@intel.com \
--cc=mark.rutland@arm.com \
--cc=mchehab+samsung@kernel.org \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=paulmck@linux.ibm.com \
--cc=robh+dt@kernel.org \
--cc=sagar.kadam@sifive.com \
--cc=yash.shah@sifive.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;
as well as URLs for NNTP newsgroup(s).