From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/6] AM35x: Add missing GPIO mux config for EHCI port
Date: Thu, 25 Feb 2010 15:03:11 -0800 [thread overview]
Message-ID: <20100225230311.26233.97139.stgit@baageli.muru.com> (raw)
In-Reply-To: <20100225230116.26233.65157.stgit@baageli.muru.com>
From: Ajay Kumar Gupta <ajay.gupta@ti.com>
Adding GPIO mux config used for PHY reset of EHCI port on base board.
We get below failure message without this patch,
"hub 1-0:1.0: unable to enumerate USB device on port 1"
Signed-off-by: Ajay Kumar Gupta <ajay.gupta@ti.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
---
arch/arm/mach-omap2/board-am3517evm.c | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/board-am3517evm.c b/arch/arm/mach-omap2/board-am3517evm.c
index e6b8967..aee0a02 100644
--- a/arch/arm/mach-omap2/board-am3517evm.c
+++ b/arch/arm/mach-omap2/board-am3517evm.c
@@ -301,6 +301,9 @@ static void __init am3517_evm_init(void)
ARRAY_SIZE(am3517_evm_devices));
omap_serial_init();
+
+ /* Configure GPIO for EHCI port */
+ omap_mux_init_gpio(57, OMAP_PIN_OUTPUT);
usb_ehci_init(&ehci_pdata);
/* DSS */
am3517_evm_display_init();
next prev parent reply other threads:[~2010-02-25 23:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 23:02 [PATCH 0/6] omap i2c init fix and trivial board changes for 2.6.34 Tony Lindgren
2010-02-25 23:03 ` [PATCH 1/6] omap: i2c: Fix muxing for command line enabled bus Tony Lindgren
2010-02-25 23:03 ` [PATCH 2/6] Zoom3: Defconfig update Tony Lindgren
2010-02-25 23:03 ` Tony Lindgren [this message]
2010-02-25 23:03 ` [PATCH 4/6] AM35x: Enable OMAP_MUX in defconfig Tony Lindgren
2010-02-25 23:03 ` [PATCH 5/6] AM3517 EVM: Enable I2C support Tony Lindgren
2010-02-25 23:03 ` [PATCH 6/6] AM3517EVM : correct typo - tca6416 mispelt as tca6516 Tony Lindgren
2010-02-26 23:36 ` [PATCH 7/6] omap2: Initialize Menelaus and MMC for N8X0 Tony Lindgren
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=20100225230311.26233.97139.stgit@baageli.muru.com \
--to=tony@atomide.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).