Re: musb otg changes break booting on omaps
On Tue, Jun 23, 2009 at 03:20:19PM +0200, ext Gupta, Ajay Kumar wrote: Looks like commit 84e250ffa76dddc1bad84e04248a27f442c25986 musb: proper hookup to transceiver drivers breaks booting on omaps if no transceiver is configured. Got any patches for that? Tony, Is this on OMAP35x EVM? If so then the below patch should help. http://marc.info/?l=linux-omapm=123907915211910w=2 and omap3x30-based hardware will most likely use twl4030-usb and in some cases (like evm) use the no-op trasceiver. -- balbi -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: musb otg changes break booting on omaps
On Tuesday 23 June 2009, Felipe Balbi wrote: Looks like commit 84e250ffa76dddc1bad84e04248a27f442c25986 musb: proper hookup to transceiver drivers breaks booting on omaps if no transceiver is configured. Got any patches for that? Tony, Is this on OMAP35x EVM? If so then the below patch should help. http://marc.info/?l=linux-omapm=123907915211910w=2 The problem with that patch is that the transceiver config is board-specific. So the omap2430.c change is wrong. Just register the NOP transceiver in the EVM setup code. and omap3x30-based hardware will most likely use twl4030-usb and in some cases (like evm) use the no-op trasceiver. I think I've got an SX51 patch somewhwere, I'll dig it up. - Dave -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
