From: sashiko-bot@kernel.org
To: "James Hilliard" <james.hilliard1@gmail.com>
Cc: dmaengine@vger.kernel.org, vkoul@kernel.org, Frank.Li@kernel.org
Subject: Re: [PATCH] dmaengine: tegra: only advertise supported pause operations
Date: Mon, 09 Nov 2026 05:09:45 +0000 [thread overview]
Message-ID: <sashiko-outbox-204415@kernel.org> (raw)
In-Reply-To: <20261108-submit-tegra186-dma-pause-caps-v1-v1-1-9cc9b17a033d@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] dmaengine: tegra: redundant pause checks in
tegra_dma_device_pause()
--
commit 3ce960c2c1d14548e97fac4df9585c921b1d04e0
Author: James Hilliard <james.hilliard1@gmail.com>
dmaengine: tegra: only advertise supported pause operations
This commit registers the device_pause and device_resume callbacks in
tegra_dma_probe() only when cdata->hw_support_pause is set, preventing SoCs
such as Tegra186 from advertising unsupported pause capabilities.
> diff --git a/drivers/dma/tegra186-gpc-dma.c b/drivers/dma/tegra186-gpc-dma.c
> index e76c58f213d84..72266f490e8a3 100644
> --- a/drivers/dma/tegra186-gpc-dma.c
> +++ b/drivers/dma/tegra186-gpc-dma.c
> @@ -1518,8 +1518,10 @@ static int tegra_dma_probe(struct platform_device *pdev)
> tdma->dma_dev.device_terminate_all = tegra_dma_terminate_all;
> tdma->dma_dev.device_tx_status = tegra_dma_tx_status;
> tdma->dma_dev.device_issue_pending = tegra_dma_issue_pending;
> - tdma->dma_dev.device_pause = tegra_dma_device_pause;
> - tdma->dma_dev.device_resume = tegra_dma_device_resume;
> + if (cdata->hw_support_pause) {
> + tdma->dma_dev.device_pause = tegra_dma_device_pause;
> + tdma->dma_dev.device_resume = tegra_dma_device_resume;
> + }
[Severity: Low]
Can the !tdc->tdma->chip_data->hw_support_pause checks in
tegra_dma_device_pause() and tegra_dma_device_resume() be dropped now that
both callbacks are only registered when cdata->hw_support_pause is true?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261108-submit-tegra186-dma-pause-caps-v1-v1-1-9cc9b17a033d@gmail.com?part=1
prev parent reply other threads:[~2026-11-09 5:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 5:00 [PATCH] dmaengine: tegra: only advertise supported pause operations James Hilliard
2026-11-09 5:09 ` sashiko-bot [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=sashiko-outbox-204415@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=james.hilliard1@gmail.com \
--cc=sashiko-reviews@lists.linux.dev \
--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