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 2/2] dt-bindings: dmaengine: Add compatible for Tegra234
Date: Thu, 7 Jul 2022 15:57:25 +0530 [thread overview]
Message-ID: <20220707102725.41383-3-akhilrajeev@nvidia.com> (raw)
In-Reply-To: <20220707102725.41383-1-akhilrajeev@nvidia.com>
Document the compatible string used by GPCDMA controller for Tegra234.
Signed-off-by: Akhil R <akhilrajeev@nvidia.com>
---
.../devicetree/bindings/dma/nvidia,tegra186-gpc-dma.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/dma/nvidia,tegra186-gpc-dma.yaml b/Documentation/devicetree/bindings/dma/nvidia,tegra186-gpc-dma.yaml
index 9dd1476d1849..81f3badbc8ec 100644
--- a/Documentation/devicetree/bindings/dma/nvidia,tegra186-gpc-dma.yaml
+++ b/Documentation/devicetree/bindings/dma/nvidia,tegra186-gpc-dma.yaml
@@ -23,6 +23,7 @@ properties:
oneOf:
- const: nvidia,tegra186-gpcdma
- items:
+ - const: nvidia,tegra234-gpcdma
- const: nvidia,tegra194-gpcdma
- const: nvidia,tegra186-gpcdma
--
2.17.1
next prev parent reply other threads:[~2022-07-07 10:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 10:27 [PATCH 0/2] Add compatible for Tegra234 GPCDMA Akhil R
2022-07-07 10:27 ` [PATCH 1/2] dmaengine: tegra: Add terminate() for Tegra234 Akhil R
2022-07-07 10:40 ` Jon Hunter
2022-07-07 10:47 ` Akhil R
2022-07-07 14:11 ` Jon Hunter
2022-07-07 10:27 ` Akhil R [this message]
2022-07-07 10:40 ` [PATCH 2/2] dt-bindings: dmaengine: Add compatible " Jon Hunter
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=20220707102725.41383-3-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).