From: Vinod Koul <vkoul@kernel.org>
To: Robin Gong <yibin.gong@nxp.com>
Cc: "l.stach@pengutronix.de" <l.stach@pengutronix.de>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
dl-linux-imx <linux-imx@nxp.com>
Subject: Re: [PATCH v3 0/4] Correct dma pool for imx-sdma
Date: Wed, 5 Dec 2018 13:53:45 +0530 [thread overview]
Message-ID: <20181205082345.GE2847@vkoul-mobl> (raw)
In-Reply-To: <1541504525-25720-1-git-send-email-yibin.gong@nxp.com>
On 06-11-18, 03:40, Robin Gong wrote:
> This patch set to correct dma pool used in the commit fe5b85c656bc
> ("dmaengine: imx-sdma: alloclate bd memory from dma pool")
> because all bds should be contiguous in memory in multi bds case
> for sdma, but dma pool can't statify it and cause transfer failure
> then.Thank Lucas for the making things on the right way.
>
> This patch set is v3 based on Lucas's V1/V2, the main refine:
> --fix the issue I reported in V1 but Lucas workaround it by improper
> way in V2.
> --add vchan_synchronize() to kill tasklet in virt-dma internal.
> --refine name: use sdma_disable_channel_async instead of
> sdma_disable_channel_with_delay since no delay indeed for
> device_terminate_all.
> Please refer to below link for more information:
> https://patchwork.kernel.org/patch/10601111
Applied all, thanks and CCed stable
--
~Vinod
prev parent reply other threads:[~2018-12-05 8:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 3:40 Robin Gong
2018-11-06 3:40 ` [PATCH v3 1/4] Revert "dmaengine: imx-sdma: Use GFP_NOWAIT for dma allocations" Robin Gong
2018-11-06 3:40 ` [PATCH v3 2/4] Revert "dmaengine: imx-sdma: alloclate bd memory from dma pool" Robin Gong
2018-11-06 3:40 ` [PATCH v3 3/4] dmaengine: imx-sdma: implement channel termination via worker Robin Gong
2018-11-06 3:40 ` [PATCH v3 4/4] dmaengine: imx-sdma: use GFP_NOWAIT for dma descriptor allocations Robin Gong
2018-11-12 15:56 ` [PATCH v3 0/4] Correct dma pool for imx-sdma Lucas Stach
2018-11-20 9:08 ` Robin Gong
2018-12-04 8:11 ` Robin Gong
2018-12-05 8:23 ` Vinod Koul [this message]
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=20181205082345.GE2847@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=l.stach@pengutronix.de \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yibin.gong@nxp.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
all inboxes | Powered by JetHome®