From: Wolfgang Grandegger <wg@grandegger.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Adding USBH2 support for mx31pdk
Date: Fri, 21 Oct 2011 15:28:17 +0200 [thread overview]
Message-ID: <4EA17371.10807@grandegger.com> (raw)
In-Reply-To: <CAOMZO5D9DGySpJZBkx96kwV4aPfux-ykGAm2s5JK-NovPE-CFA@mail.gmail.com>
Hi Fabio,
On 10/21/2011 02:54 PM, Fabio Estevam wrote:
> Hi Stefano,
>
> I am trying to add USBH2 support for MX31PDK and I am using qong code
> as reference.
>
> When I add the USB related defines in mx31pdk.h (same as qong.h) :
>
> /* USB */
> #define CONFIG_CMD_USB
> #ifdef CONFIG_CMD_USB
> #define CONFIG_USB_EHCI /* Enable EHCI USB support */
> #define CONFIG_USB_EHCI_MXC
> #define CONFIG_EHCI_HCD_INIT_AFTER_RESET
> #define CONFIG_MXC_USB_PORT 2
> #define CONFIG_MXC_USB_PORTSC (MXC_EHCI_MODE_ULPI | MXC_EHCI_UTMI_8BIT)
> #define CONFIG_MXC_USB_FLAGS MXC_EHCI_POWER_PINS_ENABLED
> #define CONFIG_EHCI_IS_TDI
> #define CONFIG_USB_STORAGE
> #define CONFIG_DOS_PARTITION
> #define CONFIG_SUPPORT_VFAT
> #define CONFIG_CMD_EXT2
> #define CONFIG_CMD_FAT
> #endif /* CONFIG_CMD_USB */
>
> , the mx31pdk board no longer boots.
>
> I also took care of the USBH2 IOMUX, but even without the IOMUX the
> board does not boot.
Is the IOMUX setup correct?
> Do you see anything obvious that I am missing here? Does qong board
> boot fine on your top of tree git?
The USB pins do need to be setup properly? Search for "usb" in qong.c
and have a look to
http://lxr.linux.no/#linux+v3.0.4/arch/arm/mach-imx/mach-mx31_3ds.c
Hope it helps.
Wolfgang.
next prev parent reply other threads:[~2011-10-21 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 12:54 [U-Boot] Adding USBH2 support for mx31pdk Fabio Estevam
2011-10-21 13:28 ` Wolfgang Grandegger [this message]
2011-10-21 14:57 ` Fabio Estevam
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=4EA17371.10807@grandegger.com \
--to=wg@grandegger.com \
--cc=u-boot@lists.denx.de \
/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