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 3/3] arm64: tegra: Update compatible for Tegra234 GPCDMA
Date: Wed, 20 Jul 2022 16:10:45 +0530 [thread overview]
Message-ID: <20220720104045.16099-4-akhilrajeev@nvidia.com> (raw)
In-Reply-To: <20220720104045.16099-1-akhilrajeev@nvidia.com>
Use the compatible specific to Tegra234 for GPCDMA to support
additional features.
Signed-off-by: Akhil R <akhilrajeev@nvidia.com>
Reviewed-by: Jon Hunter <jonathanh@nvidia.com>
---
arch/arm64/boot/dts/nvidia/tegra234.dtsi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm64/boot/dts/nvidia/tegra234.dtsi b/arch/arm64/boot/dts/nvidia/tegra234.dtsi
index cf611eff7f6b..c3d2e48994d1 100644
--- a/arch/arm64/boot/dts/nvidia/tegra234.dtsi
+++ b/arch/arm64/boot/dts/nvidia/tegra234.dtsi
@@ -22,8 +22,8 @@
ranges = <0x0 0x0 0x0 0x40000000>;
gpcdma: dma-controller@2600000 {
- compatible = "nvidia,tegra194-gpcdma",
- "nvidia,tegra186-gpcdma";
+ compatible = "nvidia,tegra234-gpcdma",
+ "nvidia,tegra186-gpcdma";
reg = <0x2600000 0x210000>;
resets = <&bpmp TEGRA234_RESET_GPCDMA>;
reset-names = "gpcdma";
--
2.17.1
next prev parent 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 [PATCH v4 0/3] Add compatible for Tegra234 GPCDMA Akhil R
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 ` Akhil R [this message]
2022-07-26 12:42 ` [PATCH v4 0/3] Add compatible for Tegra234 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=20220720104045.16099-4-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;
as well as URLs for NNTP newsgroup(s).