From: Ming Lei <ming.lei@canonical.com>
To: Chris Ball <cjb@laptop.org>
Cc: linux-mmc@vger.kernel.org, Ming Lei <ming.lei@canonical.com>
Subject: [PATCH] MMC: OMAP: make MMC_OMAP* depend on DMA_OMAP
Date: Thu, 5 Jul 2012 09:12:01 +0800 [thread overview]
Message-ID: <1341450721-20993-1-git-send-email-ming.lei@canonical.com> (raw)
Recent commits on omap mmc/hsmmc in -next tree switch to
DMA_ENGINE entirely, so make MMC_OMAP* depend on DMA_OMAP
and DMA_ENGINE, otherwise OMAP MMC/HSMMC won't work without
enabling DMA_ENGINE and DMA_OMAP.
The patch simply make them depend on DMA_OMAP since DMA_OMAP
will select DMA_ENGINE automatically.
Signed-off-by: Ming Lei <ming.lei@canonical.com>
---
drivers/mmc/host/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/mmc/host/Kconfig b/drivers/mmc/host/Kconfig
index aa131b3..ef72c50 100644
--- a/drivers/mmc/host/Kconfig
+++ b/drivers/mmc/host/Kconfig
@@ -231,7 +231,7 @@ config MMC_SDHCI_S3C_DMA
config MMC_OMAP
tristate "TI OMAP Multimedia Card Interface support"
- depends on ARCH_OMAP
+ depends on ARCH_OMAP && DMA_OMAP
select TPS65010 if MACH_OMAP_H2
help
This selects the TI OMAP Multimedia card Interface.
@@ -242,7 +242,7 @@ config MMC_OMAP
config MMC_OMAP_HS
tristate "TI OMAP High Speed Multimedia Card Interface support"
- depends on SOC_OMAP2430 || ARCH_OMAP3 || ARCH_OMAP4
+ depends on (SOC_OMAP2430 || ARCH_OMAP3 || ARCH_OMAP4) && DMA_OMAP
help
This selects the TI OMAP High Speed Multimedia card Interface.
If you have an OMAP2430 or OMAP3 board or OMAP4 board with a
--
1.7.9.5
next reply other threads:[~2012-07-05 1:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 1:12 Ming Lei [this message]
2012-07-10 3:13 ` [PATCH] MMC: OMAP: make MMC_OMAP* depend on DMA_OMAP Chris Ball
2012-07-19 5:05 ` Chris Ball
2012-07-19 11:29 ` S, Venkatraman
2012-07-19 14:41 ` Chris Ball
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=1341450721-20993-1-git-send-email-ming.lei@canonical.com \
--to=ming.lei@canonical.com \
--cc=cjb@laptop.org \
--cc=linux-mmc@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.