Re: [PATCH v5 00/14] usb: phy: msm: Fixes, cleanups and DT support

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

 



On Mon, 2014-03-24 at 17:25 +0200, Ivan T. Ivanov wrote:

> 
> > If you are
> > booting from RAM (doing something like 'fastboot boot boot.img' to
> > start the kernel), then could you try instead writing the kernel to
> > flash and booting directly to it, without first going into fastboot,
> > and let me know what happens.  In my situation, clearly there's some
> > element of hardware setup that fastboot does that my kernel can rely
> > upon for working, that my kernel alone does not perform.
> 
> I will look what aboot is doing and add same sequence to driver.

It was small, but important difference. There is MUX, which selects 
which port to be used by USB2.0 controller. On DragonBord8074 it
should be second one. This is what "qcom,phy-num" DT property supposed
to select. Unfortunately this is not enough. Register 0xfd4ab000 should
contain value different than zero. Example of this can be seen in
qcom,dwc3 driver [1].

Regards,
Ivan

[1] http://thread.gmane.org/gmane.linux.documentation/14549

> 
> > 
> > Thanks for any info you can provide.
> >  -- Tim
> 


--
To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [Linux for Sparc]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux