devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eddie James <eajames@linux.ibm.com>
To: linux-aspeed@lists.ozlabs.org
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	mark.rutland@arm.com, jason@lakedaemon.net, maz@kernel.org,
	robh+dt@kernel.org, tglx@linutronix.de, joel@jms.id.au,
	andrew@aj.id.au, eajames@linux.ibm.com
Subject: [PATCH v5 09/12] ARM: dts: aspeed: ast2500: Add XDMA Engine
Date: Thu,  9 Jan 2020 14:59:00 -0600	[thread overview]
Message-ID: <20200109205903.27036-10-eajames@linux.ibm.com> (raw)
In-Reply-To: <20200109205903.27036-1-eajames@linux.ibm.com>

Add a node for the XDMA engine with all the necessary information.

Signed-off-by: Eddie James <eajames@linux.ibm.com>
Reviewed-by: Andrew Jeffery <andrew@aj.id.au>
---
 arch/arm/boot/dts/aspeed-g5.dtsi | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/arch/arm/boot/dts/aspeed-g5.dtsi b/arch/arm/boot/dts/aspeed-g5.dtsi
index 1c40c8f5b431..f3fb65982cfc 100644
--- a/arch/arm/boot/dts/aspeed-g5.dtsi
+++ b/arch/arm/boot/dts/aspeed-g5.dtsi
@@ -1,5 +1,6 @@
 // SPDX-License-Identifier: GPL-2.0+
 #include <dt-bindings/clock/aspeed-clock.h>
+#include <dt-bindings/interrupt-controller/aspeed-scu-ic.h>
 
 / {
 	model = "Aspeed BMC";
@@ -259,6 +260,17 @@ gfx: display@1e6e6000 {
 				interrupts = <0x19>;
 			};
 
+			xdma: xdma@1e6e7000 {
+				compatible = "aspeed,ast2500-xdma";
+				reg = <0x1e6e7000 0x100>;
+				clocks = <&syscon ASPEED_CLK_GATE_BCLK>;
+				resets = <&syscon ASPEED_RESET_XDMA>;
+				interrupts-extended = <&vic 6>, <&scu_ic ASPEED_AST2500_SCU_IC_PCIE_RESET_LO_TO_HI>;
+				pcie-device = "bmc";
+				aspeed,scu = <&syscon>;
+				status = "disabled";
+			};
+
 			adc: adc@1e6e9000 {
 				compatible = "aspeed,ast2500-adc";
 				reg = <0x1e6e9000 0xb0>;
-- 
2.24.0


  parent reply	other threads:[~2020-01-09 20:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-09 20:58 [PATCH v5 00/12] aspeed: Add SCU interrupt controller and XDMA engine drivers Eddie James
2020-01-09 20:58 ` [PATCH v5 01/12] dt-bindings: interrupt-controller: Add Aspeed SCU interrupt controller Eddie James
2020-01-09 20:58 ` [PATCH v5 02/12] irqchip: " Eddie James
2020-01-09 20:58 ` [PATCH v5 03/12] ARM: dts: aspeed: ast2500: Add " Eddie James
2020-01-09 20:58 ` [PATCH v5 04/12] ARM: dts: aspeed: ast2600: Add SCU interrupt controllers Eddie James
2020-01-09 20:58 ` [PATCH v5 05/12] dt-bindings: soc: Add Aspeed XDMA Engine Eddie James
2020-01-09 20:58 ` [PATCH v5 06/12] soc: aspeed: Add XDMA Engine Driver Eddie James
2020-01-09 20:58 ` [PATCH v5 07/12] soc: aspeed: xdma: Add user interface Eddie James
2020-01-09 20:58 ` [PATCH v5 08/12] soc: aspeed: xdma: Add reset ioctl Eddie James
2020-01-09 20:59 ` Eddie James [this message]
2020-01-09 20:59 ` [PATCH v5 10/12] ARM: dts: aspeed: ast2600: Add XDMA Engine Eddie James
2020-01-09 20:59 ` [PATCH v5 11/12] ARM: dts: aspeed: witherspoon: Enable " Eddie James
2020-01-09 20:59 ` [PATCH v5 12/12] ARM: dts: aspeed: tacoma: Enable XDMA engine Eddie James

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=20200109205903.27036-10-eajames@linux.ibm.com \
    --to=eajames@linux.ibm.com \
    --cc=andrew@aj.id.au \
    --cc=devicetree@vger.kernel.org \
    --cc=jason@lakedaemon.net \
    --cc=joel@jms.id.au \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=tglx@linutronix.de \
    /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).