Skip to contentSkip to conversation

Status of clock patches after mainline reset? Case: Beagle C2 and EHCI

DISCUSSION Paul Walmsley 1 participant 2 messages May 23, 2009 – Jun 5, 2009 1 message not in the archive

lore
Share & tools
lore

Paul Walmsley

author
#1 lore raw
In reply to a message not in the archive

Hi Jarkko

Quoted 9 lines · Jarkko Nikula

EHCI port is not working on my Beagle C2 with linux-omap but is working with this one:

http://www.angstrom-distribution.org/demo/beagleboard/uImage-2.6.28-r17-beagleboard.bin

Looks like the error below was fixed by the 205f37af718984ec67444bccc888cd575531bce1 but got reseted with Tony's eba05254cb561dc27d5664503f91f7c21954e648.

Quoted 5 lines

ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Drive Clock usbhost_48m_fck didn't enable in 100000 tries ehci-omap ehci-omap.0: OMAP-EHCI Host Controller

Is this re-fixed with your last week set, in PM branch etc?

Unfortunately, no. Looking at the patches, this seems to have been one of the upstream clock merge casualties.

I will try to get a fix series out soon for 2.6.30-rcX for this.

Thanks for the detailed bug report -

- Paul

author
#2 lore raw

Hi Jarkko,

Quoted 15 lines · Paul Walmsley
Quoted 13 lines · Jarkko Nikula

EHCI port is not working on my Beagle C2 with linux-omap but is working with this one:

http://www.angstrom-distribution.org/demo/beagleboard/uImage-2.6.28-r17-beagleboard.bin

Looks like the error below was fixed by the 205f37af718984ec67444bccc888cd575531bce1 but got reseted with Tony's eba05254cb561dc27d5664503f91f7c21954e648.

ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Drive Clock usbhost_48m_fck didn't enable in 100000 tries ehci-omap ehci-omap.0: OMAP-EHCI Host Controller

Quoted 6 lines
Quoted 1 line

Is this re-fixed with your last week set, in PM branch etc?

Unfortunately, no. Looking at the patches, this seems to have been one of the upstream clock merge casualties.

I will try to get a fix series out soon for 2.6.30-rcX for this.

A quick update on this; it seems unlikely that this will make it into 2.6.30 but it is next on my to-do list, so we'll shoot for 2.6.31 fixes.

- Paul