RE: MX25 USB timeout on ID 0951:1665 Kingston Technology Digital DataTraveler SE9 64GB

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

 



 
> On Mon, Jan 15, 2018 at 2:35 PM, Michael Nazzareno Trimarchi
> <michael@xxxxxxxxxxxxxxxxxxxx> wrote:
> > Hi Peter
> >
> > On Mon, Dec 25, 2017 at 1:56 AM, Peter Chen <peter.chen@xxxxxxx> wrote:
> >>
> >>> > On Thu, Nov 16, 2017 at 10:20 AM, Peter Chen <peter.chen@xxxxxxx>
> wrote:
> >>> >>
> >>> >>> >
> >>> >>> > All USB registers, including USB transceiver, USB non-core, and USB
> core.
> >>> >>>
> >>> >>> I need to have some time to go to the platform again. It will be
> >>> >>> possible this
> >>> weekend.
> >>> >>> Have you any idea to restrict the debug apart register dump?
> >>> >>>
> >>> >>
> >>> >> I am afraid I don't have since imx25 is too old, I have little
> >>> >> directly experiences on
> >>> it.
> >>> >>
> >>> >
> >>> > I have done some testing on top. I can not easily dump registers
> >>> > on the 2.6.31. I have recompile the old kernel and re-instrumented it.
> >>> > Well I don't find any important thing.
> >>> >
> >>> > The old kernel was using ehci_fsl.c basecode and the new one use
> >>> > chipidea. Let's say that some changes are in USB_CTRL usbmisc
> >>> > controller initialization but even play with those bits I did not
> >>> > find any failure on that side. I will continue on difference. Hope
> >>> > that some other have some idea ;).
> >>>
> >>> I have used a usb hardware tracer. What I can say that basically
> >>> after the reset the device try to go in HIGH SPEED mode but the
> >>> controller can only manage full speed even is an ehci.
> >>>
> >>> I have tried the errata to set PFSC bit but is even set from the dts
> >>> if we force the FULL SPEED mode.
> >
> > The big difference I found is the way that they schedule request in
> > periodic schedule introduce by
> > 3ca9aebac2ebb8f56d2d097636b8c568320a9f87 from v3.10
> >
> 
> After reading all the code and check every registers. I discovered that problem is
> before kernel start. For now is a magic mistery. I need to check bootloader source
> code. Old kernel and new kernel works in old bootloader. I need to understand what
> is done in the bootloader that make kernel not perfect working
> 
 
I am glad you are close to answer :) 

Peter
��.n��������+%������w��{.n�����{���)��jg��������ݢj����G�������j:+v���w�m������w�������h�����٥




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

  Powered by Linux