From: Thomas Weber <weber@corscience.de>
To: linux-omap@vger.kernel.org
Cc: Thomas Weber <weber@corscience.de>
Subject: [PATCH] OMAP: omap-mcbsp: Fix building after replacement
Date: Thu, 20 Jan 2011 15:12:11 +0100 [thread overview]
Message-ID: <1295532731-5438-1-git-send-email-weber@corscience.de> (raw)
Fix building omap-mcbsp after replacing ARCH_OMAP24x0 in
commit 8a9c1aa6a4caa7db1c2fca4b47168af9077e0f95.
> omap: Start using CONFIG_SOC_OMAP
>
> We want to have just CONFIG_ARCH_OMAP2, 3 and 4. The rest
> are nowadays just subcategories of these.
>
> Search and replace the following:
>
> ARCH_OMAP2420 SOC_OMAP2420
> ARCH_OMAP2430 SOC_OMAP2430
> ARCH_OMAP3430 SOC_OMAP3430
Signed-off-by: Thomas Weber <weber@corscience.de>
---
sound/soc/omap/omap-mcbsp.c | 1 +
sound/soc/omap/omap-mcbsp.h | 1 +
2 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/sound/soc/omap/omap-mcbsp.c b/sound/soc/omap/omap-mcbsp.c
index 3cc293b..ede6afd 100644
--- a/sound/soc/omap/omap-mcbsp.c
+++ b/sound/soc/omap/omap-mcbsp.c
@@ -113,6 +113,7 @@ static const int omap44xx_dma_reqs[][2] = {
static const int omap44xx_dma_reqs[][2] = {};
#endif
+#if defined(CONFIG_SOC_OMAP2420)
static const unsigned long omap2420_mcbsp_port[][2] = {
{ OMAP24XX_MCBSP1_BASE + OMAP_MCBSP_REG_DXR1,
OMAP24XX_MCBSP1_BASE + OMAP_MCBSP_REG_DRR1 },
diff --git a/sound/soc/omap/omap-mcbsp.h b/sound/soc/omap/omap-mcbsp.h
index b7b0ce1..37dc721 100644
--- a/sound/soc/omap/omap-mcbsp.h
+++ b/sound/soc/omap/omap-mcbsp.h
@@ -54,6 +54,7 @@ enum omap_mcbsp_div {
#undef NUM_LINKS
#define NUM_LINKS 4
#endif
+#if defined(CONFIG_ARCH_OMAP3) || defined(CONFIG_SOC_OMAP2430)
#undef NUM_LINKS
#define NUM_LINKS 5
#endif
--
1.7.4.rc2
next reply other threads:[~2011-01-20 14:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 14:12 Thomas Weber [this message]
2011-01-20 15:08 ` [PATCH] OMAP: omap-mcbsp: Fix building after replacement Poddar, Sourav
2011-01-20 18:19 ` Tony Lindgren
2011-01-21 6:25 ` Varadarajan, Charulatha
2011-01-21 7:28 ` Jarkko Nikula
2011-01-21 7:30 ` Varadarajan, Charulatha
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=1295532731-5438-1-git-send-email-weber@corscience.de \
--to=weber@corscience.de \
--cc=linux-omap@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox