Re: USB OTG doesn't work in HOST mode on OMAP3 processor on 3.18-rc5

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Dec 01, 2014 at 08:57:14AM +0100, Yegor Yefremov wrote:
> On Sat, Nov 29, 2014 at 4:35 PM, Felipe Balbi <balbi@xxxxxx> wrote:
> > Hi,
> >
> > On Fri, Nov 28, 2014 at 11:35:53AM +0100, Yegor Yefremov wrote:
> >> On Wed, Nov 19, 2014 at 6:53 PM, Tony Lindgren <tony@xxxxxxxxxxx> wrote:
> >> > * Enric Balletbo Serra <eballetbo@xxxxxxxxx> [141119 03:14]:
> >> >> 2014-11-18 16:42 GMT+01:00 Tony Lindgren <tony@xxxxxxxxxxx>:
> >> >>
> >> >> Checked again, and no luck. It's very weird because from the OTG point
> >> >> of view, OTG is exactly the same between Beagleboard-XM and IGEPv2.
> >> >>
> >> >> Can you confirm that you're using kernel 3.18-rc5 without other
> >> >> patches applied ? At this moment, I don't have a Beagleboard-XM to
> >> >> test, I'll try to get one because at this moment I'm a bit stuck with
> >> >> this problem.
> >> >
> >> > Yes it was with v3.18-rc5 and the defconfig patch I posted except
> >> > I had to disable all the other MUSB platforms. Also tested it with
> >> > built in modules.
> >> >
> >> > Maybe you need to check the .dts pinctrl entries for hsusb0_* lines?
> >>
> >> Just my 2 cents, My am335x based board shows similar symptoms
> >> (CONFIG_USB_MUSB_DUAL_ROLE enabled). Only if I specify  dr_mode =
> >> "host"; in my DTS I get device enumerated. 3.15, that I had before
> >> made no problems as OTG.
> >
> > Are you sure your ID pin is properly routed ? If you set dr_mode to otg,
> > then you *must* have a properly routed ID pin and use a proper
> > micro-/mini-ab receptacle. That's not true for e.g. beagle bone black.
> >
> > One USB port is using a Standard-A while the other uses mini-B. You
> > can't do any role swapping with those.
> 
> Yes, I'm sure, that ID pin is routed properly. It is also not BBB, but
> real device Baltos iR 5221
> (http://visionsystems.de/produkte/baltos-ir-5221.html). With 3.15 I'm
> able to use OTG port both as device and host. I boot the device,
> insert FTDI based hardware into OTG port and my ttyUSBx devices, then
> disconnect and connect to PC and I get usb0 network interface and can
> communicate with PC.

if you know it works on v3.15, then you have a bisection point. Can you
bisect it down to one commit ?

-- 
balbi

Attachment: signature.asc
Description: Digital signature


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux