From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v3 2/6] dma: rcar-dma: Added dma_pause operation to rcar_dma driver
Date: Thu, 15 Oct 2015 15:18:20 +0000 [thread overview]
Message-ID: <45156037.ECkKFSIJeV@avalon> (raw)
In-Reply-To: <1443559488-2416-3-git-send-email-hamzahfrq.sub@gmail.com>
Hi Muhammad,
Thank you for the patch.
On Tuesday 29 September 2015 22:44:44 hamzahfrq.sub@gmail.com wrote:
> From: Muhammad Hamza Farooq <mfarooq@visteon.com>
>
> Signed-off-by: Muhammad Hamza Farooq <mfarooq@visteon.com>
> ---
> drivers/dma/sh/rcar-dmac.c | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
>
> diff --git a/drivers/dma/sh/rcar-dmac.c b/drivers/dma/sh/rcar-dmac.c
> index 2b28291..c7cd4ed 100644
> --- a/drivers/dma/sh/rcar-dmac.c
> +++ b/drivers/dma/sh/rcar-dmac.c
> @@ -774,6 +774,26 @@ static void rcar_dmac_chan_reinit(struct rcar_dmac_chan
> *chan) }
> }
>
> +static int rcar_dmac_chan_pause(struct dma_chan *chan)
> +{
> + u32 chcr;
> + int ret;
> + unsigned long flags;
> + struct rcar_dmac_chan *rchan = to_rcar_dmac_chan(chan);
> +
> + spin_lock_irqsave(&rchan->lock, flags);
> +
> + chcr = rcar_dmac_chan_read(rchan, RCAR_DMACHCR);
> + chcr &= ~RCAR_DMACHCR_DE;
> + rcar_dmac_chan_write(rchan, RCAR_DMACHCR, chcr);
> + ret = rcar_dmac_wait_stop(rchan);
The DMA engine API documents the pause operation as stopping DMA transfers in
a resumable way without data loss. Doesn't stopping the transfer forcefully
like this result in incomplete transfers and thus data loss ? Shouldn't we
instead signal the pause request to the interrupt handler to avoid starting
the next transfer and wait for the end of the current transfer ?
> +
> + spin_unlock_irqrestore(&rchan->lock, flags);
> +
> + WARN_ON(ret < 0);
> + return ret;
> +}
> +
> static void rcar_dmac_stop(struct rcar_dmac *dmac)
> {
> rcar_dmac_write(dmac, RCAR_DMAOR, 0);
> @@ -1740,6 +1760,7 @@ static int rcar_dmac_probe(struct platform_device
> *pdev) engine->device_prep_slave_sg = rcar_dmac_prep_slave_sg;
> engine->device_prep_dma_cyclic = rcar_dmac_prep_dma_cyclic;
> engine->device_config = rcar_dmac_device_config;
> + engine->device_pause = rcar_dmac_chan_pause;
> engine->device_terminate_all = rcar_dmac_chan_terminate_all;
> engine->device_tx_status = rcar_dmac_tx_status;
> engine->device_issue_pending = rcar_dmac_issue_pending;
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2015-10-15 15:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 20:44 [PATCH v3 2/6] dma: rcar-dma: Added dma_pause operation to rcar_dma driver hamzahfrq.sub
2015-10-15 15:18 ` Laurent Pinchart [this message]
2015-10-19 21:16 ` Hamza Farooq
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=45156037.ECkKFSIJeV@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-sh@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.