From: Felipe Balbi <balbi@kernel.org>
To: Andrey Konovalov <andreyknvl@google.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
USB list <linux-usb@vger.kernel.org>,
Dmitry Vyukov <dvyukov@google.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>
Subject: Re: Recommended USB3/SuperSpeed gadget device
Date: Wed, 29 Apr 2020 19:57:37 +0300 [thread overview]
Message-ID: <877dxy1b7i.fsf@kernel.org> (raw)
In-Reply-To: <CAAeHK+yRMBFX4zgYLSLECdnM54GoEYcbocTDw=GrGrAD+cJ1bA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 869 bytes --]
Hi,
Andrey Konovalov <andreyknvl@google.com> writes:
>> If you're not willing to do that, I anything using dwc3 (dragonboard,
>> beaglebone AI, and many many others) would be good here.
>
> All DragonBoards that I found have USB 2.0 device ports AFAIU, but
Oh, they put a USB2.0 only connector. That sucks, as it actually has
dwc3 inside.
> BeagleBone AI looks like what I need. Thanks!
beware that beaglebone AI runs quite hot. Get yourself some beefy
heatsink and a fan. Also, make sure to get the non-standard serial cable.
> While looking for a board with USB 3.0 device support, I've also found
> the UP board [1]. I'm not sure which driver it uses though.
>
> [1] https://up-board.org/up/specifications/
It uses dwc3. It's Intel CherryTrail inside. Heikki and Andy (Cc) should
have information about those, hopefully.
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2020-04-29 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 22:36 Recommended USB3/SuperSpeed gadget device Andrey Konovalov
2020-04-29 2:23 ` Andrey Konovalov
2020-04-29 7:39 ` Felipe Balbi
2020-04-29 13:42 ` Andrey Konovalov
2020-04-29 16:57 ` Felipe Balbi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877dxy1b7i.fsf@kernel.org \
--to=balbi@kernel.org \
--cc=andreyknvl@google.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dvyukov@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.