From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/6] usb: dwc2: Add support for SPLIT transactions
Date: Tue, 26 Jan 2016 20:52:03 -0700 [thread overview]
Message-ID: <56A83EE3.3030304@wwwdotorg.org> (raw)
In-Reply-To: <1453000196-4752-1-git-send-email-stefan.bruens@rwth-aachen.de>
On 01/16/2016 08:09 PM, Stefan Br?ns wrote:
> The first patch fixes an out-of-bounds access, and makes the calculation of
> maximum transfer size more straightforward. It also makes overriding the
> maximum transfer size easier for split transactions
Sorry I haven't been keeping up on the U-Boot dwc2 patches. Is this
series still pending, or was it replaced with something else? It doesn't
apply cleanly on top of u-boot/master.
The good news is that with u-boot/master (b72ae192e39f "Merge branch
'master' of git://git.denx.de/u-boot-video") both USB keyboards I have
work perfectly on both a model A and a model B, including keyboard
repeat. That's great work; thanks very much!
next prev parent reply other threads:[~2016-01-27 3:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-17 3:09 [U-Boot] [PATCH 0/6] usb: dwc2: Add support for SPLIT transactions Stefan Brüns
2016-01-17 3:09 ` [U-Boot] [PATCH 1/6] usb: dwc2: Fix out-of-bounds access, fix chunk size Stefan Brüns
2016-01-17 3:09 ` [U-Boot] [PATCH 2/6] usb: dwc2: Simplify wait_for_chhltd(), remove ignore_ack Stefan Brüns
2016-01-17 3:09 ` [U-Boot] [PATCH 3/6] usb: dwc2: split transfer core from outer loop Stefan Brüns
2016-01-17 3:09 ` [U-Boot] [PATCH 4/6] usb: dwc2: add helper function for setting SPLIT HC registers Stefan Brüns
2016-01-17 3:09 ` [U-Boot] [PATCH 5/6] usb: dwc2: Implement SPLIT transaction support Stefan Brüns
2016-01-17 3:09 ` [U-Boot] [PATCH 6/6] usb: dwc2: Add SPLIT INTERRUPT " Stefan Brüns
2016-01-18 17:21 ` [U-Boot] [PATCH 0/6] usb: dwc2: Add support for SPLIT transactions Marek Vasut
2016-01-27 3:52 ` Stephen Warren [this message]
2016-01-27 4:05 ` Marek Vasut
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=56A83EE3.3030304@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=u-boot@lists.denx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox