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

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

[Paul Walmsley]

Hi Jarkko

On Fri, 22 May 2009, Jarkko Nikula wrote:

> 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
>
> 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

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

[Paul Walmsley]

Hi Jarkko,

On Sat, 23 May 2009, Paul Walmsley wrote:

> On Fri, 22 May 2009, Jarkko Nikula wrote:
> 
> > 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
> >
> > 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