From: Robin Gong <yibin.gong@nxp.com>
To: "vkoul@kernel.org" <vkoul@kernel.org>,
"l.stach@pengutronix.de" <l.stach@pengutronix.de>
Cc: "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: [PATCH v3 4/4] dmaengine: imx-sdma: use GFP_NOWAIT for dma descriptor allocations
Date: Tue, 6 Nov 2018 03:40:37 +0000 [thread overview]
Message-ID: <1541504525-25720-5-git-send-email-yibin.gong@nxp.com> (raw)
In-Reply-To: <1541504525-25720-1-git-send-email-yibin.gong@nxp.com>
From: Lucas Stach <l.stach@pengutronix.de>
DMA buffer descriptors aren't allocated from atomic context, so they
can use the less heavyweigth GFP_NOWAIT.
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
Signed-off-by: Robin Gong <yibin.gong@nxp.com>
---
drivers/dma/imx-sdma.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/dma/imx-sdma.c b/drivers/dma/imx-sdma.c
index 03d46f1..cb1b44d 100644
--- a/drivers/dma/imx-sdma.c
+++ b/drivers/dma/imx-sdma.c
@@ -1214,7 +1214,7 @@ static int sdma_alloc_bd(struct sdma_desc *desc)
int ret = 0;
desc->bd = dma_zalloc_coherent(NULL, bd_size, &desc->bd_phys,
- GFP_ATOMIC);
+ GFP_NOWAIT);
if (!desc->bd) {
ret = -ENOMEM;
goto out;
--
2.7.4
next prev parent reply other threads:[~2018-11-06 3:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 3:40 [PATCH v3 0/4] Correct dma pool for imx-sdma 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 ` Robin Gong [this message]
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
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=1541504525-25720-5-git-send-email-yibin.gong@nxp.com \
--to=yibin.gong@nxp.com \
--cc=dmaengine@vger.kernel.org \
--cc=l.stach@pengutronix.de \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vkoul@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).