[patch-v2.6.39 6/7] OMAP4430: hwmod data: Adding USBOTG

[balbi@ti.com (Felipe Balbi)]

Hi all,

On Fri, Feb 18, 2011 at 03:11:11PM +0100, Cousson, Benoit wrote:
> On 2/17/2011 7:18 PM, Tony Lindgren wrote:
> > * Cousson, Benoit<b-cousson@ti.com>  [110217 09:45]:
> >>
> >> Done, boot tested, and that does remove the warning about the
> >> missing opt clock you had with the previous data.
> >>
> >> git://gitorious.org/omap-pm/linux.git for_2.6.39/omap4_hwmod_data
> >>
> >> Just let me know if it does break anything else.
> > 
> > Pulled into omap-for-linus. Also now merged are the devel-hwspinlock
> > and devel-mcspi branches.
> 
> McSPI OMAP4 hwmod data are missing a couple of flags that break the boot for the moment.
> 
> Govindraj should rebase on the omap4_hwmod_data branch and add the missing rev and dev_attr for the McSPI.
> 
> Unfortunately, even with that patch omap-for-linus boot hangs after the following trace:
> 
> [    0.875091] omap_device: omap2_mcspi.1: new worst case activate latency 0: 30517
> [    0.886657] usbcore: registered new interface driver usbfs
> [    0.892822] usbcore: registered new interface driver hub
> [    0.898681] usbcore: registered new device driver usb
> [    0.904815] omap_i2c omap_i2c.1: bus 1 rev4.0 at 400 kHz

I tested your branch merged with mine and it was working fine. What else
is on omap-for-linus ? There are only 28 patches on that branch, a
bisect would be quick ?

-- 
balbi