From: Alexander Holler <holler@ahsoftware.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/3] omap3_beagle: enable EHCI and USB storage.
Date: Thu, 26 May 2011 17:41:03 +0200 [thread overview]
Message-ID: <4DDE748F.1070007@ahsoftware.de> (raw)
In-Reply-To: <4DDE39E3.70700@gmail.com>
Am 26.05.2011 13:30, schrieb Christian Spielberger:
> Hi Alexander Holler,
>
> is EHCI on omap3 already working?
>
> On my beagleboard xM
>
> usb start
>
> hangs at this position in method ehci_hcd_init:
>
> + /* perform TLL soft reset, and wait until reset is complete */
> + writel(OMAP_USBTLL_SYSCONFIG_SOFTRESET,
> + OMAP3_USBTLL_BASE + OMAP_USBTLL_SYSCONFIG);
It works on a normal BeagleBoard (720 MHz). On the XM it seems you have
either move the initialization of the usb-clocks a bit upwards (e.g.
before the reset of the phy) or you have to add a check if the clock
runs after it was initialized (before that writel). The XM seems to be
too fast and the peripheral-clock isn't ready when that writel wants to
write to the peripheral-register, therefor it hangs there on a XM.
But even than USB doesn't seem to work on a BeagleBoard XM (at least
some people told me so). I don't have a XM, so I can't help more there.
It might be a problem with (a needed reset of) the HUB which is included
on the XM, I don't know.
And a side note: don't try a kernel compiled with gcc 4.6 on the
BeagleBoard. EHCI on the OMAP3 doesn't come up here when the kernel is
compiled with gcc 4.6. That seems to be specific to OMAP, I don't have
those problems on other ARM hw (I use successfull e.g. EHCI on some
armv5 devices with kernels which are compiled with gcc 4.6).When I
compile the same kernel using gcc 4.5.2 I have no problems with EHCI on
the BeagleBoard. Haven't investigated that further.
Regards,
Alexander
next prev parent reply other threads:[~2011-05-26 15:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 11:30 [U-Boot] [PATCH 3/3] omap3_beagle: enable EHCI and USB storage Christian Spielberger
2011-05-26 15:41 ` Alexander Holler [this message]
2011-05-27 7:34 ` Alexander Holler
2011-05-27 9:40 ` Christian Spielberger
2011-05-27 11:24 ` Alexander Holler
2011-05-28 8:55 ` Christian Spielberger
-- strict thread matches above, loose matches on Subject: below --
2011-04-01 22:37 [U-Boot] [PATCH 1/3] OMAP3: Change some USB related MUX settings to values used by the kernel Alexander Holler
2011-04-01 22:37 ` [U-Boot] [PATCH 3/3] omap3_beagle: enable EHCI and USB storage Alexander Holler
2011-04-19 13:33 ` Paulraj, Sandeep
2011-04-01 22:16 [U-Boot] [PATCH 1/3] OMAP3: Change some USB related MUX settings to values used by the kernel Alexander Holler
2011-04-01 22:16 ` [U-Boot] [PATCH 3/3] omap3_beagle: enable EHCI and USB storage Alexander Holler
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=4DDE748F.1070007@ahsoftware.de \
--to=holler@ahsoftware.de \
--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