From: Robin Murphy <robin.murphy@arm.com>
To: vkoul@kernel.org
Cc: dmaengine@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [PATCH 7/9] dmaengine: ste_dma40: Drop local dma_parms
Date: Thu, 3 Sep 2020 21:25:51 +0100 [thread overview]
Message-ID: <011a956183b92a258bf0922385d145ea966dcbea.1599164692.git.robin.murphy@arm.com> (raw)
In-Reply-To: <cover.1599164692.git.robin.murphy@arm.com>
Since commit 9495b7e92f71 ("driver core: platform: Initialize dma_parms
for platform devices"), struct platform_device already provides a
dma_parms structure, so we can save allocating another one.
Signed-off-by: Robin Murphy <robin.murphy@arm.com>
---
drivers/dma/ste_dma40.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/dma/ste_dma40.c b/drivers/dma/ste_dma40.c
index 21e2f1d0c210..6b10d5c935a0 100644
--- a/drivers/dma/ste_dma40.c
+++ b/drivers/dma/ste_dma40.c
@@ -535,7 +535,6 @@ struct d40_gen_dmac {
* mode" allocated physical channels.
* @num_log_chans: The number of logical channels. Calculated from
* num_phy_chans.
- * @dma_parms: DMA parameters for the channel
* @dma_both: dma_device channels that can do both memcpy and slave transfers.
* @dma_slave: dma_device channels that can do only do slave transfers.
* @dma_memcpy: dma_device channels that can do only do memcpy transfers.
@@ -577,7 +576,6 @@ struct d40_base {
int num_memcpy_chans;
int num_phy_chans;
int num_log_chans;
- struct device_dma_parameters dma_parms;
struct dma_device dma_both;
struct dma_device dma_slave;
struct dma_device dma_memcpy;
@@ -3641,7 +3639,6 @@ static int __init d40_probe(struct platform_device *pdev)
if (ret)
goto destroy_cache;
- base->dev->dma_parms = &base->dma_parms;
ret = dma_set_max_seg_size(base->dev, STEDMA40_MAX_SEG_SIZE);
if (ret) {
d40_err(&pdev->dev, "Failed to set dma max seg size\n");
--
2.28.0.dirty
next prev parent reply other threads:[~2020-09-03 20:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 20:25 [PATCH 0/9] dmaengine: Tidy up dma_parms Robin Murphy
2020-09-03 20:25 ` [PATCH 1/9] dmaengine: axi-dmac: Drop local dma_parms Robin Murphy
2020-09-03 20:25 ` [PATCH 2/9] dmaengine: bcm2835: " Robin Murphy
2020-09-03 20:25 ` [PATCH 3/9] dmaengine: imx-dma: " Robin Murphy
2020-09-03 20:25 ` [PATCH 4/9] dmaengine: imx-sdma: " Robin Murphy
2020-09-03 20:25 ` [PATCH 5/9] dmaengine: mxs: " Robin Murphy
2020-09-03 20:25 ` [PATCH 6/9] dmaengine: rcar-dmac: " Robin Murphy
2020-09-03 20:25 ` Robin Murphy [this message]
2020-09-03 20:25 ` [PATCH 8/9] dmaengine: qcom: bam_dma: " Robin Murphy
2020-09-03 20:25 ` [PATCH 9/9] dmaengine: pl330: " Robin Murphy
2020-09-11 12:12 ` [PATCH 0/9] dmaengine: Tidy up dma_parms 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=011a956183b92a258bf0922385d145ea966dcbea.1599164692.git.robin.murphy@arm.com \
--to=robin.murphy@arm.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.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).