Re: USB3.0 DWC3 can't work with latest Linux-4.9.rc7

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

 



On 05.12.2016 13:00, Felipe Balbi wrote:

(no top-posting, please)

Hi,

it helps if you include maintainers for correct
drivers. scripts/get_maintainer.pl helps a lot.

Jerry Huang <jerry.huang@xxxxxxx> writes:
And I tested USB2.0 disk, with Sriram's 6 patches, it works well. So Just USB3.0 can't work.

BTW,
The board with USB3.0 DWC3 controller and the USB3.0 disk work well with Linux-4.1.8.

alright, in that case you can bisect. Please do so and find the first
commit when this started happening.

-----Original Message-----
From: Jerry Huang
Sent: Monday, December 05, 2016 6:11 PM
To: stern@xxxxxxxxxxxxxxxxxxx; linux-usb@xxxxxxxxxxxxxxx
Cc: Sriram Dash <sriram.dash@xxxxxxx>
Subject: USB3.0 DWC3 can't work with latest Linux-4.9.rc7

Hi, Guys,
1. I tested the USB3.0 DWC3 with latest Linux-4.9-rc7 on LS1043ardb board.
But I got the below errors, this error is returned from dma_supported(dev, mask) while running " dma_set_mask_and_coherent" in function " xhci_plat_probe".
...
[    0.756166] xhci-hcd: probe of xhci-hcd.0.auto failed with error -5
[    0.762438] xhci-hcd: probe of xhci-hcd.1.auto failed with error -5
[    0.768712] xhci-hcd: probe of xhci-hcd.2.auto failed with error -5
[    0.775049] usbcore: registered new interface driver usb-storage
...

2. Then, I applied 6 patches from Sriram:
https://patchwork.kernel.org/patch/9434163/
https://patchwork.kernel.org/patch/9434155/
https://patchwork.kernel.org/patch/9434131/
https://patchwork.kernel.org/patch/9434165/
https://patchwork.kernel.org/patch/9434167/
https://patchwork.kernel.org/patch/9434133/

however, I got another error as below shows when I attach one USB disk to this board.
It seems USB device return the 8 bytes descriptor, but all 8 byte data driver read  are zero from the buffer received.
Has any comment for this issue?

usb 2-1: new SuperSpeed USB device number 2 using xhci-hcd
[  164.323396] usb 2-1: device descriptor read/8, error -61

hmm, connection refused. Mathias, any idea?


usb/core/message.c  usb_get_descritptor() sets the -61 (ENODATA) if
the control transfer received data,  but the descriptor type byte doesn't match.
(as the 8 zeros probably would do)

does xhci verbose debugging show any control transfer related messages during this?

echo -n 'module xhci_hcd =p' > /sys/kernel/debug/dynamic_debug/control

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



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

  Powered by Linux