Alan,
On Tue, Oct 30, 2012 at 9:34 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Tue, 30 Oct 2012, Mohan V wrote:
Device not getting detected when
connected---
/ # [ 135.621002] usbhs_wakeup: Enabling clocks
[ 135.625762]
Alan,
On Mon, Oct 29, 2012 at 8:54 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Mon, 29 Oct 2012, Mohan V wrote:
I'm not going to be able to help very much with an Android kernel.
Does the same problem occur with a vanilla non-Android 3.6 kernel? If
it doesn't, that indicates the
On Tue, 30 Oct 2012, Mohan V wrote:
Device not getting detected when
connected---
/ # [ 135.621002] usbhs_wakeup: Enabling clocks
[ 135.625762] usbhs_runtime_resume:++
[ 135.630371] usbhs_runtime_resume:--
[
Alan,
On Fri, Oct 26, 2012 at 8:49 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Fri, 26 Oct 2012, Mohan V wrote:
When the USB bus is in suspend, a device connected to OHCI port does
not get detected, whereas the device connected to EHCI port is getting
detected.
Can you provide
On Mon, 29 Oct 2012, Mohan V wrote:
I'm not going to be able to help very much with an Android kernel.
Does the same problem occur with a vanilla non-Android 3.6 kernel? If
it doesn't, that indicates the problem was caused by some
Android-specific changes.
With the vanilla 3.6 kernel,
On Fri, 26 Oct 2012, Mohan V wrote:
When the USB bus is in suspend, a device connected to OHCI port does
not get detected, whereas the device connected to EHCI port is getting
detected.
Can you provide a dmesg log showing the OHCI problem with
CONFIG_USB_DEBUG enabled?
Please find
