From: "H. Nikolaus Schaller" <hns@goldelico.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: kyungmin.park@samsung.com,
Miquel Raynal <miquel.raynal@bootlin.com>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tony Lindgren <tony@atomide.com>,
linux-mtd@lists.infradead.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux-OMAP <linux-omap@vger.kernel.org>,
Discussions about the Letux Kernel
<letux-kernel@openphoenux.org>
Subject: Re: [PATCH] mtd: onenand: omap2: Pass correct flags for prep_dma_memcpy
Date: Sat, 4 Jan 2020 09:46:23 +0100 [thread overview]
Message-ID: <9EB362B8-EA81-445C-9FD7-29ABB890100C@goldelico.com> (raw)
In-Reply-To: <20200104073453.16077-1-peter.ujfalusi@ti.com>
> Am 04.01.2020 um 08:34 schrieb Peter Ujfalusi <peter.ujfalusi@ti.com>:
>
> The commit converting the driver to DMAengine was missing the flags for
> the memcpy prepare call.
> It went unnoticed since the omap-dma drive was ignoring them.
s/drive/driver/
>
> Fixes: 3ed6a4d1de2c5 (" mtd: onenand: omap2: Convert to use dmaengine for memcp")
> Reported-by: Aaro Koskinen <aaro.koskinen@iki.fi>
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
> ---
> Hi,
>
> Aaro reported [1] a failure on omap2-onenand pointing to
> 4689d35c765c696bdf0535486a990038b242a26b. It looks like the root cause is the
> conversion of omap2-onenand to DMAengine which missed the flags.
>
> Basically the client is waiting for a callback without asking for it. This
> certainly causes timeout.
>
> I have not tested the patch, but it should fix the issue.
makes the gta04a5one.dts work again.
Tested-by: H. Nikolaus Schaller <hns@goldelico.com>
BR and thanks!
Nikolaus
>
> [1] https://lore.kernel.org/lkml/20200103081726.GD15023@darkstar.musicnaut.iki.fi/
>
> drivers/mtd/nand/onenand/omap2.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/mtd/nand/onenand/omap2.c b/drivers/mtd/nand/onenand/omap2.c
> index edf94ee54ec7..71a632b815aa 100644
> --- a/drivers/mtd/nand/onenand/omap2.c
> +++ b/drivers/mtd/nand/onenand/omap2.c
> @@ -328,7 +328,8 @@ static inline int omap2_onenand_dma_transfer(struct omap2_onenand *c,
> struct dma_async_tx_descriptor *tx;
> dma_cookie_t cookie;
>
> - tx = dmaengine_prep_dma_memcpy(c->dma_chan, dst, src, count, 0);
> + tx = dmaengine_prep_dma_memcpy(c->dma_chan, dst, src, count,
> + DMA_CTRL_ACK | DMA_PREP_INTERRUPT);
> if (!tx) {
> dev_err(&c->pdev->dev, "Failed to prepare DMA memcpy\n");
> return -EIO;
> --
> Peter
>
> Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
> Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
>
next prev parent reply other threads:[~2020-01-04 8:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-04 7:34 [PATCH] mtd: onenand: omap2: Pass correct flags for prep_dma_memcpy Peter Ujfalusi
2020-01-04 8:46 ` H. Nikolaus Schaller [this message]
2020-01-04 20:29 ` Aaro Koskinen
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=9EB362B8-EA81-445C-9FD7-29ABB890100C@goldelico.com \
--to=hns@goldelico.com \
--cc=aaro.koskinen@iki.fi \
--cc=kyungmin.park@samsung.com \
--cc=letux-kernel@openphoenux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=peter.ujfalusi@ti.com \
--cc=tony@atomide.com \
--cc=vigneshr@ti.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).