From: mporter@ti.com (Matt Porter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 5/9] dmaengine: edma: Add TI EDMA device tree binding
Date: Tue, 5 Mar 2013 15:53:11 -0500 [thread overview]
Message-ID: <1362516795-6346-6-git-send-email-mporter@ti.com> (raw)
In-Reply-To: <1362516795-6346-1-git-send-email-mporter@ti.com>
The binding definition is based on the generic DMA controller
binding.
Signed-off-by: Matt Porter <mporter@ti.com>
---
Documentation/devicetree/bindings/dma/ti-edma.txt | 49 +++++++++++++++++++++
1 file changed, 49 insertions(+)
create mode 100644 Documentation/devicetree/bindings/dma/ti-edma.txt
diff --git a/Documentation/devicetree/bindings/dma/ti-edma.txt b/Documentation/devicetree/bindings/dma/ti-edma.txt
new file mode 100644
index 0000000..075a60e3
--- /dev/null
+++ b/Documentation/devicetree/bindings/dma/ti-edma.txt
@@ -0,0 +1,49 @@
+TI EDMA
+
+Required properties:
+- compatible : "ti,edma3"
+- ti,hwmods: Name of the hwmods associated to the EDMA
+- ti,edma-regions: Number of regions
+- ti,edma-slots: Number of slots
+- ti,edma-queue-tc-map: List of transfer control to queue mappings
+- ti,edma-queue-priority-map: List of queue priority mappings
+- ti,edma-default-queue: Default queue value
+
+Optional properties:
+- ti,edma-reserved-channels: List of reserved channel regions
+- ti,edma-reserved-slots: List of reserved slot regions
+- ti,edma-xbar-event-map: Crossbar event to channel map
+
+Example:
+
+edma: edma at 49000000 {
+ reg = <0x49000000 0x10000>;
+ interrupt-parent = <&intc>;
+ interrupts = <12 13 14>;
+ compatible = "ti,edma3";
+ ti,hwmods = "tpcc", "tptc0", "tptc1", "tptc2";
+ #dma-cells = <1>;
+ dma-channels = <64>;
+ ti,edma-regions = <4>;
+ ti,edma-slots = <256>;
+ ti,edma-reserved-channels = <0 2
+ 14 2
+ 26 6
+ 48 4
+ 56 8>;
+ ti,edma-reserved-slots = <0 2
+ 14 2
+ 26 6
+ 48 4
+ 56 8
+ 64 127>;
+ ti,edma-queue-tc-map = <0 0
+ 1 1
+ 2 2>;
+ ti,edma-queue-priority-map = <0 0
+ 1 1
+ 2 2>;
+ ti,edma-default-queue = <0>;
+ ti,edma-xbar-event-map = <1 12
+ 2 13>;
+};
--
1.7.9.5
next prev parent reply other threads:[~2013-03-05 20:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-05 20:53 [PATCH v8 0/9] DMA Engine support for AM33XX Matt Porter
2013-03-05 20:53 ` [PATCH v8 1/9] ARM: davinci: move private EDMA API to arm/common Matt Porter
2013-03-05 20:53 ` [PATCH v8 2/9] ARM: edma: remove unused transfer controller handlers Matt Porter
2013-03-05 20:53 ` [PATCH v8 3/9] ARM: edma: add AM33XX support to the private EDMA API Matt Porter
2013-03-05 20:53 ` [PATCH v8 4/9] dmaengine: edma: enable build for AM33XX Matt Porter
2013-03-05 20:53 ` Matt Porter [this message]
2013-03-05 20:53 ` [PATCH v8 6/9] ARM: dts: add AM33XX EDMA support Matt Porter
2013-03-06 4:19 ` Kumar, Anil
[not found] ` <a02b3a2e7dff42b0814bb6fa603068ba@DFLE73.ent.ti.com>
2013-03-06 14:01 ` Matt Porter
2013-03-05 20:53 ` [PATCH v8 7/9] spi: omap2-mcspi: convert to dma_request_slave_channel_compat() Matt Porter
2013-03-05 20:53 ` [PATCH v8 8/9] spi: omap2-mcspi: add generic DMA request support to the DT binding Matt Porter
2013-03-05 20:53 ` [PATCH v8 9/9] ARM: dts: add AM33XX SPI DMA support Matt Porter
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=1362516795-6346-6-git-send-email-mporter@ti.com \
--to=mporter@ti.com \
--cc=linux-arm-kernel@lists.infradead.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).