linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/5] ARM: mxs/mx23evk: add dma device
Date: Sat, 5 Feb 2011 10:08:15 +0800	[thread overview]
Message-ID: <1296871696-21008-5-git-send-email-shawn.guo@freescale.com> (raw)
In-Reply-To: <1296871696-21008-1-git-send-email-shawn.guo@freescale.com>

Signed-off-by: Shawn Guo <shawn.guo@freescale.com>
---
 arch/arm/mach-mxs/Kconfig        |    1 +
 arch/arm/mach-mxs/mach-mx23evk.c |    8 ++++++++
 2 files changed, 9 insertions(+), 0 deletions(-)

diff --git a/arch/arm/mach-mxs/Kconfig b/arch/arm/mach-mxs/Kconfig
index cd2fbdf..0b9bb03 100644
--- a/arch/arm/mach-mxs/Kconfig
+++ b/arch/arm/mach-mxs/Kconfig
@@ -19,6 +19,7 @@ config MACH_MX23EVK
 	bool "Support MX23EVK Platform"
 	select SOC_IMX23
 	select MXS_HAVE_AMBA_DUART
+	select MXS_HAVE_PLATFORM_DMA
 	default y
 	help
 	  Include support for MX23EVK platform. This includes specific
diff --git a/arch/arm/mach-mxs/mach-mx23evk.c b/arch/arm/mach-mxs/mach-mx23evk.c
index aa06400..13c22a0 100644
--- a/arch/arm/mach-mxs/mach-mx23evk.c
+++ b/arch/arm/mach-mxs/mach-mx23evk.c
@@ -37,6 +37,14 @@ static void __init mx23evk_init(void)
 	mxs_iomux_setup_multiple_pads(mx23evk_pads, ARRAY_SIZE(mx23evk_pads));
 
 	mx23_add_duart();
+
+	/*
+	 * the order of adding dma device matters here, otherwise
+	 * dma_device.dev_id may differ from mxs_dma_engine.dev_id,
+	 * in which case mxs-dma will fail to probe.
+	 */
+	mx23_add_apbh_dma();
+	mx23_add_apbx_dma();
 }
 
 static void __init mx23evk_timer_init(void)
-- 
1.7.1

  parent reply	other threads:[~2011-02-05  2:08 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-05  2:08 Add dma support for i.MX23/28 Shawn Guo
2011-02-05  2:08 ` [PATCH 1/5] dmaengine: mxs-dma: add " Shawn Guo
2011-02-04 18:17   ` Russell King - ARM Linux
2011-02-08 22:56     ` Shawn Guo
2011-02-08 16:38       ` Russell King - ARM Linux
2011-02-05 15:33   ` Russell King - ARM Linux
2011-02-08 22:59     ` Shawn Guo
2011-02-07  7:37   ` Lothar Waßmann
2011-02-08 23:09     ` Shawn Guo
2011-02-07  8:25   ` Sascha Hauer
2011-02-07  9:09     ` Russell King - ARM Linux
2011-02-08 23:28     ` Shawn Guo
2011-02-09  8:34       ` Sascha Hauer
2011-02-09 21:42         ` Shawn Guo
2011-02-07 14:13   ` Lothar Waßmann
2011-02-08 23:30     ` Shawn Guo
2011-02-07 14:31   ` Lothar Waßmann
2011-02-08 23:38     ` Shawn Guo
2011-02-08 14:41   ` Lothar Waßmann
2011-02-09  0:17     ` Shawn Guo
2011-02-09  8:06       ` Lothar Waßmann
2011-02-09 20:42         ` Shawn Guo
2011-02-09 13:13           ` Lothar Waßmann
2011-02-14  0:16         ` Shawn Guo
2011-02-09  9:09     ` Sascha Hauer
2011-02-09 21:02       ` Shawn Guo
2011-02-05  2:08 ` [PATCH 2/5] ARM: mxs: add dma channel definitions Shawn Guo
2011-02-05  2:08 ` [PATCH 3/5] ARM: mxs: dynamically allocate dma device for mx23/28 Shawn Guo
2011-02-07  8:09   ` Sascha Hauer
2011-02-09  0:22     ` Shawn Guo
2011-02-05  2:08 ` Shawn Guo [this message]
2011-02-05  2:08 ` [PATCH 5/5] ARM: mxs/mx28evk: add dma device Shawn Guo

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=1296871696-21008-5-git-send-email-shawn.guo@freescale.com \
    --to=shawn.guo@freescale.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).