From: Frank Li <Frank.Li@nxp.com>
To: Vinod Koul <vkoul@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>
Cc: dmaengine@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, imx@lists.linux.dev,
Frank Li <Frank.Li@nxp.com>,
Shengjiu Wang <shengjiu.wang@nxp.com>,
Vipul Kumar <vipul_kumar@mentor.com>,
Srikanth Krishnakar <Srikanth_Krishnakar@mentor.com>,
Robin Gong <yibin.gong@nxp.com>
Subject: [PATCH 2/4] dmaengine: imx-sdma: Support 24bit/3bytes for sg mode
Date: Sun, 03 Mar 2024 23:32:54 -0500 [thread overview]
Message-ID: <20240303-sdma_upstream-v1-2-869cd0165b09@nxp.com> (raw)
In-Reply-To: <20240303-sdma_upstream-v1-0-869cd0165b09@nxp.com>
From: Shengjiu Wang <shengjiu.wang@nxp.com>
Update 3bytes buswidth that is supported by sdma.
Signed-off-by: Shengjiu Wang <shengjiu.wang@nxp.com>
Signed-off-by: Vipul Kumar <vipul_kumar@mentor.com>
Signed-off-by: Srikanth Krishnakar <Srikanth_Krishnakar@mentor.com>
Acked-by: Robin Gong <yibin.gong@nxp.com>
Signed-off-by: Frank Li <Frank.Li@nxp.com>
---
drivers/dma/imx-sdma.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/dma/imx-sdma.c b/drivers/dma/imx-sdma.c
index 9a6d8f1e9ff63..ef45420485dac 100644
--- a/drivers/dma/imx-sdma.c
+++ b/drivers/dma/imx-sdma.c
@@ -176,6 +176,7 @@
#define SDMA_DMA_BUSWIDTHS (BIT(DMA_SLAVE_BUSWIDTH_1_BYTE) | \
BIT(DMA_SLAVE_BUSWIDTH_2_BYTES) | \
+ BIT(DMA_SLAVE_BUSWIDTH_3_BYTES) | \
BIT(DMA_SLAVE_BUSWIDTH_4_BYTES))
#define SDMA_DMA_DIRECTIONS (BIT(DMA_DEV_TO_MEM) | \
@@ -1659,6 +1660,9 @@ static struct dma_async_tx_descriptor *sdma_prep_slave_sg(
if (count & 3 || sg->dma_address & 3)
goto err_bd_out;
break;
+ case DMA_SLAVE_BUSWIDTH_3_BYTES:
+ bd->mode.command = 3;
+ break;
case DMA_SLAVE_BUSWIDTH_2_BYTES:
bd->mode.command = 2;
if (count & 1 || sg->dma_address & 1)
--
2.34.1
next prev parent reply other threads:[~2024-03-04 4:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 4:32 [PATCH 0/4] dmaengine: fsl-sdma: Some improvement for fsl-sdma Frank Li
2024-03-04 4:32 ` [PATCH 1/4] dmaengine: imx-sdma: Support allocate memory from internal SRAM (iram) Frank Li
2024-03-06 9:55 ` Alexander Stein
2024-03-06 15:23 ` Frank Li
2024-03-07 8:22 ` Joy Zou
2024-03-04 4:32 ` Frank Li [this message]
2024-03-07 9:05 ` [PATCH 2/4] dmaengine: imx-sdma: Support 24bit/3bytes for sg mode Joy Zou
2024-03-04 4:32 ` [PATCH 3/4] dmaengine: imx-sdma: Add multi fifo for DEV_TO_DEV Frank Li
2024-03-07 9:06 ` Joy Zou
2024-03-04 4:32 ` [PATCH 4/4] dmaengine: imx-sdma: Add i2c dma support Frank Li
2024-03-04 11:12 ` Fabio Estevam
2024-03-05 15:39 ` Frank Li
2024-03-06 8:24 ` Daniel Baluta
2024-03-07 8:34 ` Joy Zou
2024-03-04 11:41 ` [PATCH 0/4] dmaengine: fsl-sdma: Some improvement for fsl-sdma Daniel Baluta
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=20240303-sdma_upstream-v1-2-869cd0165b09@nxp.com \
--to=frank.li@nxp.com \
--cc=Srikanth_Krishnakar@mentor.com \
--cc=dmaengine@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=shengjiu.wang@nxp.com \
--cc=vipul_kumar@mentor.com \
--cc=vkoul@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