From: Mohan Kumar <mkumard@nvidia.com>
To: <vkoul@kernel.org>, <robh+dt@kernel.org>,
<thierry.reding@gmail.com>, <jonathanh@nvidia.com>,
<ldewangan@nvidia.com>, <krzysztof.kozlowski+dt@linaro.org>
Cc: <dmaengine@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
<devicetree@vger.kernel.org>, Mohan Kumar <mkumard@nvidia.com>
Subject: [PATCH V1 1/2] dt-bindings: dma: Add dma-channel-mask to nvidia,tegra210-adma
Date: Mon, 9 Oct 2023 12:05:08 +0530 [thread overview]
Message-ID: <20231009063509.2269-2-mkumard@nvidia.com> (raw)
In-Reply-To: <20231009063509.2269-1-mkumard@nvidia.com>
- Add dma-channel-mask binding doc support to nvidia,tegra210-adma
to reserve the adma channel usage
Signed-off-by: Mohan Kumar <mkumard@nvidia.com>
---
.../devicetree/bindings/dma/nvidia,tegra210-adma.yaml | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/dma/nvidia,tegra210-adma.yaml b/Documentation/devicetree/bindings/dma/nvidia,tegra210-adma.yaml
index 4003dbe94940..877147e95ecc 100644
--- a/Documentation/devicetree/bindings/dma/nvidia,tegra210-adma.yaml
+++ b/Documentation/devicetree/bindings/dma/nvidia,tegra210-adma.yaml
@@ -53,6 +53,9 @@ properties:
ADMA_CHn_CTRL register.
const: 1
+ dma-channel-mask:
+ maxItems: 1
+
required:
- compatible
- reg
--
2.17.1
next prev parent reply other threads:[~2023-10-09 6:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 6:35 [PATCH V1 0/2] Support dma channel mask Mohan Kumar
2023-10-09 6:35 ` Mohan Kumar [this message]
2023-10-10 16:21 ` [PATCH V1 1/2] dt-bindings: dma: Add dma-channel-mask to nvidia,tegra210-adma Rob Herring
2023-10-09 6:35 ` [PATCH V1 2/2] dmaengine: tegra210-adma: Support dma-channel-mask property Mohan Kumar
2023-10-16 11:09 ` [PATCH V1 0/2] Support dma channel mask Vinod Koul
2023-10-16 11:14 ` Mohan Kumar D
2023-10-16 11:22 ` Vinod Koul
2023-12-11 15:04 ` 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=20231009063509.2269-2-mkumard@nvidia.com \
--to=mkumard@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=ldewangan@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--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).