On 15 September 2014 19:06, Andrew Bresticker <abrestic@xxxxxxxxxxxx> wrote: > On Mon, Sep 15, 2014 at 12:00 AM, Tomeu Vizoso <tomeu@xxxxxxxxxxxxxxx> wrote: >> On 12 September 2014 18:37, Andrew Bresticker <abrestic@xxxxxxxxxxxx> wrote: >>> On Tue, Sep 9, 2014 at 1:21 AM, Tomeu Vizoso <tomeu@xxxxxxxxxxxxxxx> wrote: >>>> On 8 September 2014 18:22, Andrew Bresticker <abrestic@xxxxxxxxxxxx> wrote: >>>>> On Mon, Sep 8, 2014 at 8:34 AM, Tomeu Vizoso <tomeu@xxxxxxxxxxxxxxx> wrote: >>>>>> On 2 September 2014 23:34, Andrew Bresticker <abrestic@xxxxxxxxxxxx> wrote: >>>>>>> >>>>>>> Tested on Venice2, Jetson TK1, and Big with a variety of USB2.0 and >>>>>>> USB3.0 memory sticks and ethernet dongles using controller firmware >>>>>>> recently posted by Andrew Chew [2]. >>>>>> >>>>>> I have had mixed results when testing this on a Jetson TK1 board. Of 8 >>>>>> USB devices I tested with, about half where probed correctly, but the >>>>>> other half repeatedly fail in hub_port_init because in the GET_STATUS >>>>>> right after the reset, the C_PORT_CONNECTION bit is set. >>>>>> >>>>>> I don't see any correlation between the failure and the kind of usb >>>>>> device, but I don't have much experience with USB implementations >>>>>> either. >>>>> >>>>> Hmm... I haven't seen that before. Which particular devices were you using? >>>> >>>> Here they are: >>>> >>>> work: >>>> >>>> Genius keyboard: 05d5:6782 >>>> Logitech mouse: 046d:c06a >>>> Denver MP3 player: 10d6:1100 >>>> Atheros Bluetooth dongle: 0cf3:3005 >>>> >>>> don't work: >>>> >>>> MCS7830 ethernet dongle: 9710:7830 >>>> Genesys Logic hub: 05e3:0608 >>> >>> I tried the hub and it works just fine for me... Have you tried this >>> on any other boards like Big or Blaze? >> >> I have a Blaze here, but haven't been able to get the external ports >> to power up. I don't have schematics nor a strong interest to get that >> fixed myself, as I can test my code just fine with the Blaze's >> internal camera and the devices that do work on the Jetson. > > Ok, since Blaze has been announced, hopefully we can post a > device-tree for it soon. > >> I'm using the firmware file that was posted recently: >> >> xhci-tegra 70090000.usb: Firmware timestamp: 2014-05-02 02:22:50 UTC, >> Falcon state 0x20 > > Yup, I'm using the same firmware. > >> If things work for you with the same sources, .config and firmware, I >> can only think of the hw being different (other hw revision?). > > That, or perhaps bootloader differences? I'm using mainline U-Boot. Also mainline here: U-Boot 2014.10-rc1-00136-g7bee1c9 (Aug 28 2014 - 15:22:05) Don't know how to check what revision of the hw I have, though. Regards, Tomeu > Stephen, Thierry, have either of you had a chance to test this series? -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
