Re: [PATCH 14/16] usb: musb: dsps: add MUSB_DEVCTL_SESSION back after removal

From: Bin Liu
Date: Fri Jul 26 2013 - 16:15:41 EST


Sebastian,

On Fri, Jul 26, 2013 at 2:55 PM, Sebastian Andrzej Siewior
<bigeasy@xxxxxxxxxxxxx> wrote:
> The bit is removed in otg_timer() because the phy gets into
> OTG_STATE_A_WAIT_BCON.
>
> Now, this is current HEAD + my stuff to get second port working. I
> downloaded v3.2 and browsed as I was looking for the workaround, never
> tested maybe I should…
>
> On v3.8 from git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git I
> don't get the second port to work. I see
>
> [ 1.989101] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
> [ 1.996361] usb usb1: New USB device strings: Mfr=3, Product=2,
> SerialNumber=1
> [ 2.004060] usb usb1: Product: MUSB HDRC host driver
> [ 2.009363] usb usb1: Manufacturer: Linux 3.8.13+ musb-hcd
> [ 2.015183] usb usb1: SerialNumber: musb-hdrc.0.auto
> [ 2.033653] hub 1-0:1.0: USB hub found
> [ 2.037861] hub 1-0:1.0: 1 port detected
>
> and nothing happens once I plug in the device.

I started thinking when I tried this git.ti.com 3.8 kernel, I might
have done 'devmem2 0x47401c60 b 0x81' to manually set the SESSION bit
after plugged a device. It was months ago, I don't quite remember what
I tested.

My build server is down this afternoon. Once it comes back next week,
I will try 3.8 again, to see how I can help on this USB1 host mode
issue. its devctl register should stay on 0x19 even nothing is
connected.

>
> Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/