From: Akhil R <akhilrajeev@nvidia.com>
To: <devicetree@vger.kernel.org>, <dmaengine@vger.kernel.org>,
<jonathanh@nvidia.com>, <kyarlagadda@nvidia.com>,
<ldewangan@nvidia.com>, <linux-kernel@vger.kernel.org>,
<linux-tegra@vger.kernel.org>, <p.zabel@pengutronix.de>,
<rgumasta@nvidia.com>, <robh+dt@kernel.org>,
<thierry.reding@gmail.com>, <nathan@kernel.org>,
<vkoul@kernel.org>, <dan.carpenter@oracle.com>
Cc: <akhilrajeev@nvidia.com>
Subject: [PATCH v2 2/2] dmaengine: tegra: Remove unused switch case
Date: Tue, 26 Apr 2022 15:49:13 +0530 [thread overview]
Message-ID: <20220426101913.43335-3-akhilrajeev@nvidia.com> (raw)
In-Reply-To: <20220426101913.43335-1-akhilrajeev@nvidia.com>
Remove unused switch case in get_transfer_param() function.
The function is not called for MEM_TO_MEM transfers.
Signed-off-by: Akhil R <akhilrajeev@nvidia.com>
---
drivers/dma/tegra186-gpc-dma.c | 4 ----
1 file changed, 4 deletions(-)
diff --git a/drivers/dma/tegra186-gpc-dma.c b/drivers/dma/tegra186-gpc-dma.c
index a0dbafa07ec9..6b8d34165176 100644
--- a/drivers/dma/tegra186-gpc-dma.c
+++ b/drivers/dma/tegra186-gpc-dma.c
@@ -830,10 +830,6 @@ static int get_transfer_param(struct tegra_dma_channel *tdc,
*slave_bw = tdc->dma_sconfig.src_addr_width;
*csr = TEGRA_GPCDMA_CSR_DMA_IO2MEM_FC;
return 0;
- case DMA_MEM_TO_MEM:
- *burst_size = tdc->dma_sconfig.src_addr_width;
- *csr = TEGRA_GPCDMA_CSR_DMA_MEM2MEM;
- return 0;
default:
dev_err(tdc2dev(tdc), "DMA direction is not supported\n");
}
--
2.17.1
next prev parent reply other threads:[~2022-04-26 10:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 10:19 [PATCH v2 0/2] Fix uninitialized variable usage in Tegra GPCDMA Akhil R
2022-04-26 10:19 ` [PATCH v2 1/2] dmaengine: tegra: Fix uninitialized variable usage Akhil R
2022-04-26 10:19 ` Akhil R [this message]
2022-05-19 18:05 ` [PATCH v2 0/2] Fix uninitialized variable usage in Tegra GPCDMA 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=20220426101913.43335-3-akhilrajeev@nvidia.com \
--to=akhilrajeev@nvidia.com \
--cc=dan.carpenter@oracle.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=kyarlagadda@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=rgumasta@nvidia.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--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).