From: panduranga_mallireddy@ti.com
To: coelho@ti.com, netdev@vger.kernel.org,
linux-omap@vger.kernel.org, linux-mmc@vger.kernel.org
Cc: ohad@wizery.com, benzyg@ti.com, pradeepgurumath@ti.com,
vishalm@ti.com, x-boudet@ti.com, naveen_jain@ti.com,
pavan_savoy@ti.com, manjunatha_halli@ti.com, tony@atomide.com,
cjb@laptop.org,
Panduranga Mallireddy <panduranga_mallireddy@ti.com>
Subject: [PATCH 1/5] omap: panda: wlan board muxing
Date: Mon, 14 Feb 2011 02:19:14 -0500 [thread overview]
Message-ID: <1297667958-22377-2-git-send-email-panduranga_mallireddy@ti.com> (raw)
In-Reply-To: <1297667958-22377-1-git-send-email-panduranga_mallireddy@ti.com>
From: Panduranga Mallireddy <panduranga_mallireddy@ti.com>
Add board muxing to support the wlan wl1271 chip that is
hardwired to mmc5 (fifth mmc controller) on the PANDA.
Based on the wlan board muxing for zoom3 by Ohad Ben-Cohen
<ohadb@ti.com>
Signed-off-by: Panduranga Mallireddy <panduranga_mallireddy@ti.com>
---
arch/arm/mach-omap2/board-omap4panda.c | 13 +++++++++++++
1 files changed, 13 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/board-omap4panda.c b/arch/arm/mach-omap2/board-omap4panda.c
index 9218862..cc9df6c 100644
--- a/arch/arm/mach-omap2/board-omap4panda.c
+++ b/arch/arm/mach-omap2/board-omap4panda.c
@@ -401,6 +401,19 @@ static int __init omap4_panda_i2c_init(void)
#ifdef CONFIG_OMAP_MUX
static struct omap_board_mux board_mux[] __initdata = {
+ /* WLAN IRQ - GPIO 53 */
+ OMAP4_MUX(GPMC_NCS3, OMAP_MUX_MODE3 | OMAP_PIN_INPUT_PULLUP),
+ /* WLAN POWER ENABLE - GPIO 43 */
+ OMAP4_MUX(GPMC_A19, OMAP_MUX_MODE3 | OMAP_PIN_OUTPUT),
+ /* WLAN SDIO: MMC5 CMD */
+ OMAP4_MUX(SDMMC5_CMD, OMAP_MUX_MODE0 | OMAP_PIN_INPUT_PULLUP),
+ /* WLAN SDIO: MMC5 CLK */
+ OMAP4_MUX(SDMMC5_CLK, OMAP_MUX_MODE0 | OMAP_PIN_INPUT_PULLUP),
+ /* WLAN SDIO: MMC5 DAT[0-3] */
+ OMAP4_MUX(SDMMC5_DAT0, OMAP_MUX_MODE0 | OMAP_PIN_INPUT_PULLUP),
+ OMAP4_MUX(SDMMC5_DAT1, OMAP_MUX_MODE0 | OMAP_PIN_INPUT_PULLUP),
+ OMAP4_MUX(SDMMC5_DAT2, OMAP_MUX_MODE0 | OMAP_PIN_INPUT_PULLUP),
+ OMAP4_MUX(SDMMC5_DAT3, OMAP_MUX_MODE0 | OMAP_PIN_INPUT_PULLUP),
{ .reg_offset = OMAP_MUX_TERMINATOR },
};
#else
--
1.5.6.3
next prev parent reply other threads:[~2011-02-14 7:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 7:19 [PATCH 0/5] Panda: Support for WLAN on WL127x panduranga_mallireddy
2011-02-14 7:19 ` panduranga_mallireddy [this message]
2011-02-14 7:19 ` [PATCH 2/5] omap: select REGULATOR_FIXED_VOLTAGE by default for panda and sdp4430 panduranga_mallireddy
2011-02-14 7:19 ` [PATCH 3/5] omap: panda: add fixed regulator device for wlan panduranga_mallireddy
2011-02-14 7:19 ` [PATCH 4/5] omap: panda: add mmc5/wl1271 device support panduranga_mallireddy
2011-02-14 7:19 ` [PATCH 5/5] OMAP: hsmmc: Enable MMC4 and MMC5 on OMAP4 platforms panduranga_mallireddy
2011-02-14 7:24 ` [PATCH 1/5] omap: panda: wlan board muxing Ohad Ben-Cohen
2011-02-14 8:01 ` panduranga
2011-02-14 8:01 ` panduranga
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=1297667958-22377-2-git-send-email-panduranga_mallireddy@ti.com \
--to=panduranga_mallireddy@ti.com \
--cc=benzyg@ti.com \
--cc=cjb@laptop.org \
--cc=coelho@ti.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=manjunatha_halli@ti.com \
--cc=naveen_jain@ti.com \
--cc=netdev@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=pavan_savoy@ti.com \
--cc=pradeepgurumath@ti.com \
--cc=tony@atomide.com \
--cc=vishalm@ti.com \
--cc=x-boudet@ti.com \
/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.