From: Keguang Zhang <keguang.zhang@gmail.com>
To: dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Vinod Koul <vkoul@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Keguang Zhang <keguang.zhang@gmail.com>
Subject: [PATCH v5 1/2] dt-bindings: dma: Add Loongson-1 DMA
Date: Thu, 28 Sep 2023 20:19:52 +0800 [thread overview]
Message-ID: <20230928121953.524608-2-keguang.zhang@gmail.com> (raw)
In-Reply-To: <20230928121953.524608-1-keguang.zhang@gmail.com>
Add devicetree binding document for Loongson-1 DMA.
Signed-off-by: Keguang Zhang <keguang.zhang@gmail.com>
---
V4 -> V5:
A newly added patch
.../bindings/dma/loongson,ls1x-dma.yaml | 64 +++++++++++++++++++
1 file changed, 64 insertions(+)
create mode 100644 Documentation/devicetree/bindings/dma/loongson,ls1x-dma.yaml
diff --git a/Documentation/devicetree/bindings/dma/loongson,ls1x-dma.yaml b/Documentation/devicetree/bindings/dma/loongson,ls1x-dma.yaml
new file mode 100644
index 000000000000..51b45d998a58
--- /dev/null
+++ b/Documentation/devicetree/bindings/dma/loongson,ls1x-dma.yaml
@@ -0,0 +1,64 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/dma/loongson,ls1x-dma.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Loongson-1 DMA Controller
+
+maintainers:
+ - Keguang Zhang <keguang.zhang@gmail.com>
+
+description: |
+ Loongson-1 DMA controller provides 3 independent channels for
+ peripherals such as NAND and AC97.
+
+properties:
+ compatible:
+ enum:
+ - loongson,ls1b-dma
+ - loongson,ls1c-dma
+
+ reg:
+ maxItems: 1
+
+ interrupts:
+ description: Each channel has a dedicated interrupt line.
+ minItems: 1
+ maxItems: 3
+
+ interrupt-names:
+ minItems: 1
+ items:
+ - pattern: ch0
+ - pattern: ch1
+ - pattern: ch2
+
+ '#dma-cells':
+ description: The single cell represents the channel index.
+ const: 1
+
+required:
+ - compatible
+ - reg
+ - interrupts
+ - interrupt-names
+ - '#dma-cells'
+
+additionalProperties: false
+
+examples:
+ - |
+ #include <dt-bindings/interrupt-controller/irq.h>
+ dma: dma-controller@1fd01160 {
+ compatible = "loongson,ls1b-dma";
+ reg = <0x1fd01160 0x18>;
+
+ interrupt-parent = <&intc0>;
+ interrupts = <13 IRQ_TYPE_EDGE_RISING>,
+ <14 IRQ_TYPE_EDGE_RISING>,
+ <15 IRQ_TYPE_EDGE_RISING>;
+ interrupt-names = "ch0", "ch1", "ch2";
+
+ #dma-cells = <1>;
+ };
--
2.39.2
next prev parent reply other threads:[~2023-09-28 12:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 12:19 [PATCH v5 0/2] Add Loongson1 dmaengine driver Keguang Zhang
2023-09-28 12:19 ` Keguang Zhang [this message]
2023-09-28 16:42 ` [PATCH v5 1/2] dt-bindings: dma: Add Loongson-1 DMA Conor Dooley
2023-10-07 5:45 ` Keguang Zhang
2023-10-07 10:34 ` Conor Dooley
2023-10-08 11:15 ` Krzysztof Kozlowski
2023-09-28 12:19 ` [PATCH v5 2/2] dmaengine: Loongson1: Add Loongson1 dmaengine driver Keguang Zhang
2023-09-28 12:46 ` Eric Schwarz
2023-10-04 7:43 ` 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=20230928121953.524608-2-keguang.zhang@gmail.com \
--to=keguang.zhang@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=robh+dt@kernel.org \
--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).