From: Vinod Koul <vinod.koul@intel.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 1/6] dma: rcar-dma: add wait after stopping dma engine
Date: Mon, 12 Oct 2015 14:56:01 +0000 [thread overview]
Message-ID: <20151012145904.GB27370@localhost> (raw)
In-Reply-To: <1443559488-2416-2-git-send-email-hamzahfrq.sub@gmail.com>
On Tue, Sep 29, 2015 at 10:44:43PM +0200, hamzahfrq.sub@gmail.com wrote:
> From: Muhammad Hamza Farooq <mfarooq@visteon.com>
>
> DMA engine does not stop instantaneously when transaction is going on
> (see datasheet). Wait has been added
Hmmm, why is threading broken in this series?
Also why is this PATCH 1/6 whereas the rest of series is v3!
Right way is to let git do this for you and use git format-patch
--subject-prefix="PATCH v3"...
You don't do these things manually, that would be terrible waste of time
Also use git send-email to keep threading
> Signed-off-by: Muhammad Hamza Farooq <mfarooq@visteon.com>
> ---
> drivers/dma/sh/rcar-dmac.c | 28 ++++++++++++++++++++++++++--
> 1 file changed, 26 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/dma/sh/rcar-dmac.c b/drivers/dma/sh/rcar-dmac.c
> index 7820d07..2b28291 100644
> --- a/drivers/dma/sh/rcar-dmac.c
> +++ b/drivers/dma/sh/rcar-dmac.c
> @@ -716,14 +716,38 @@ static int rcar_dmac_fill_hwdesc(struct rcar_dmac_chan *chan,
> /* -----------------------------------------------------------------------------
> * Stop and reset
> */
> +#define NR_READS_TO_WAIT 5 /* number of times to check if DE = 0 */
> +static inline int rcar_dmac_wait_stop(struct rcar_dmac_chan *chan)
> +{
> + unsigned int i = 0;
> +
> + do {
> + u32 chcr = rcar_dmac_chan_read(chan, RCAR_DMACHCR);
> +
> + if (!(chcr & RCAR_DMACHCR_DE))
> + return 0;
> + cpu_relax();
> + dev_dbg(chan->chan.device->dev, "DMA xfer couldn't be stopped");
And user has no way of knowing this on production system
> + } while (++i < NR_READS_TO_WAIT);
>
> -static void rcar_dmac_chan_halt(struct rcar_dmac_chan *chan)
> + return -EBUSY;
> +}
> +
> +/* Called with chan lock held */
> +static int rcar_dmac_chan_halt(struct rcar_dmac_chan *chan)
> {
> - u32 chcr = rcar_dmac_chan_read(chan, RCAR_DMACHCR);
> + u32 chcr;
> + int ret;
>
> + chcr = rcar_dmac_chan_read(chan, RCAR_DMACHCR);
> chcr &= ~(RCAR_DMACHCR_DSE | RCAR_DMACHCR_DSIE | RCAR_DMACHCR_IE |
> RCAR_DMACHCR_TE | RCAR_DMACHCR_DE);
> rcar_dmac_chan_write(chan, RCAR_DMACHCR, chcr);
> + ret = rcar_dmac_wait_stop(chan);
> +
> + WARN_ON(ret < 0);
What if we have broken board and will see dmesg storm for this, perhaps
WARN_ON_ONCE and also would be helpful to use the verbose version and print
some meaningful message
--
~Vinod
next prev parent reply other threads:[~2015-10-12 14:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 20:44 [PATCH 1/6] dma: rcar-dma: add wait after stopping dma engine hamzahfrq.sub
2015-10-12 14:56 ` Vinod Koul [this message]
2015-10-15 15:58 ` Laurent Pinchart
2015-10-15 16:02 ` Hamza Farooq
2015-10-15 16:08 ` Hamza Farooq
2015-10-15 20:42 ` Laurent Pinchart
2015-10-19 20:54 ` Hamza Farooq
2015-10-19 21:06 ` Laurent Pinchart
2015-10-20 12:30 ` Hamza Farooq
2016-06-08 10:05 ` Kuninori Morimoto
2016-06-08 14:23 ` Laurent Pinchart
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=20151012145904.GB27370@localhost \
--to=vinod.koul@intel.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 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).