From: Akhil R <akhilrajeev@nvidia.com>
To: <dmaengine@vger.kernel.org>, <jonathanh@nvidia.com>,
<ldewangan@nvidia.com>, <linux-kernel@vger.kernel.org>,
<linux-tegra@vger.kernel.org>, <p.zabel@pengutronix.de>,
<thierry.reding@gmail.com>, <vkoul@kernel.org>,
<robh+dt@kernel.org>, <devicetree@vger.kernel.org>
Cc: <akhilrajeev@nvidia.com>
Subject: [PATCH v4 0/3] Add compatible for Tegra234 GPCDMA
Date: Wed, 20 Jul 2022 16:10:42 +0530 [thread overview]
Message-ID: <20220720104045.16099-1-akhilrajeev@nvidia.com> (raw)
In cases where the client bus gets corrupted or if the end device
ceases to send/receive data, the DMA could wait for the data forever.
Tegra234 supports recovery of such channels hung in flush mode.
Add a separate compatible for Tegra234 so that this scenario can be
handled in the driver.
v3->v4:
* Updated binding doc to use enum for compatible instead of const
v2->v3:
* Updated binding docs and device tree compatible
v1->v2:
* split device tree change to a different patch.
* Update commit message
Akhil R (3):
dt-bindings: dmaengine: Add compatible for Tegra234
dmaengine: tegra: Add terminate() for Tegra234
arm64: tegra: Update compatible for Tegra234 GPCDMA
.../bindings/dma/nvidia,tegra186-gpc-dma.yaml | 4 ++-
arch/arm64/boot/dts/nvidia/tegra234.dtsi | 4 +--
drivers/dma/tegra186-gpc-dma.c | 26 +++++++++++++++++--
3 files changed, 29 insertions(+), 5 deletions(-)
--
2.17.1
next reply other threads:[~2022-07-20 10:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 10:40 Akhil R [this message]
2022-07-20 10:40 ` [PATCH v4 1/3] dt-bindings: dmaengine: Add compatible for Tegra234 Akhil R
2022-07-25 22:22 ` Rob Herring
2022-07-20 10:40 ` [PATCH v4 2/3] dmaengine: tegra: Add terminate() " Akhil R
2022-07-20 10:40 ` [PATCH v4 3/3] arm64: tegra: Update compatible for Tegra234 GPCDMA Akhil R
2022-07-26 12:42 ` [PATCH v4 0/3] Add " 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=20220720104045.16099-1-akhilrajeev@nvidia.com \
--to=akhilrajeev@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--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