linux-kernel - Re: musb: am3358: having problem with high-speed on usb1 at peripheral

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 18 Aug 2016 11:08:40 -0500
From:   Bin Liu <b-liu@...com>
To:     ayaka <ayaka@...lik.info>
CC:     <linux-usb@...r.kernel.org>, Felipe Balbi <balbi@...nel.org>,
        <gregkh@...uxfoundation.org>, <linux-kernel@...r.kernel.org>
Subject: Re: musb: am3358: having problem with high-speed on usb1 at
 peripheral

Hi,

On Fri, Aug 12, 2016 at 10:23:15AM +0800, ayaka wrote:
> Hello all:
>   I recently add a support for customize am3358 board using the branch
> processor-sdk-linux-03.00.00 from Ti git. But I meet a problem with musb
> at the peripheral mode.
>   I have force usb1 in peripheral mode in dts as it only have USB_DP,
> USB_DM and USBDRV connected. I start up a ether gadget using the configfs,

Do you mean USB1_DRVVBUS pin? If so, you have wrong hw design. For
peripheral mode, you should float this pin, but connect USB1_VBUS pin
instead.

Regards,
-Bin.

> But I found it would always work on the USB 2.0 full speed mode,
> even the testmode can't force it in high speed mode or it won't appear
> at host side. If I want it work at high speed mode, what should I do?
>   I also meet the DMA problem, I have to apply the "ARM: dts: am33xx: 
> fix DMA support for the second USB interface", but does patches really
> work? Although it make the error message disapear, but the mail list
> said the just make the usb back to PIO mode.
> 
> -- 
> 2.7.4
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-usb" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html